TwinTemporarilyUnavailableError

Thrown on a 503: the Twin service could neither carry out the request nor answer it truthfully. The request is unchanged and safe to retry as-is — unlike TwinPermissionsConflictError, which never clears on its own.

Hierarchy

• Error
  • TwinTemporarilyUnavailableError

Index

Constructors

• constructor

Properties

• errorBody
• retryAfterSeconds

Constructors

constructor

• new TwinTemporarilyUnavailableError(message: string, errorBody?: TwinErrorBody, retryAfterSeconds?: number): TwinTemporarilyUnavailableError

• Overrides Error.constructor

  Parameters

  • message: string

  • optionalerrorBody: TwinErrorBody

  • optionalretryAfterSeconds: number

  Returns TwinTemporarilyUnavailableError

Properties

publicoptionalreadonlyerrorBody

errorBody?: TwinErrorBody

publicoptionalreadonlyretryAfterSeconds

retryAfterSeconds?: number

The Retry-After the service sent, in seconds, when it sent one. The Twin service pairs the status with this header deliberately, so that "retrying is worthwhile" does not rest on the status alone — pass it to whatever backoff the caller uses instead of inventing a delay.