WorkflowWorldError
WorkflowWorldError is the base error class for failures originating from a workflow world (storage backend). World implementations (local, Postgres, Vercel) throw subclasses of this error when storage operations fail.
You can use instanceof WorkflowWorldError to catch any World-related error regardless of the specific type. The static .is() method only matches errors constructed directly as WorkflowWorldError. Use the subclass-specific .is() methods (for example, EntityConflictError.is()) to match specific error types.
Most world errors are handled automatically by the Workflow runtime. You will typically only encounter these errors when interacting with world storage APIs directly or when there are infrastructure-level issues.
API signature
Properties
| Name | Type | Description |
|---|---|---|
status | number | HTTP status code from the world backend, if available. |
code | string | Machine-readable error code, if available. |
url | string | The URL that was requested, if available. |
retryAfter | number | Retry-After value in seconds, present on 429 and 425 responses. |
message | string | The error message. |
Static methods
WorkflowWorldError.is(value)
Type-safe check that matches only errors constructed directly as WorkflowWorldError. Does not match subclasses like EntityConflictError. Use instanceof to catch all world errors, or the subclass-specific .is() methods.
Subclasses
The following error types extend WorkflowWorldError:
EntityConflictError: operation conflicts with entity stateRunExpiredError: run has expiredTooEarlyError: request made before system is readyThrottleError: request was rate-limited