Engine error
Something failed inside SignEnvoy that was not your request's fault.
| Problem type | /problems/engine-error |
|---|---|
| HTTP status | 500 |
| Emitted by | Signing page, Dashboard (JSON requests), REST API (/v1) |
| Title values | Engine error |
| Trigger |
REST API (/v1):
unmapped engine failure
|
What happened
The engine raised an error that maps to no specific problem type, or the gateway encountered an unexpected failure. The response is HTTP 500.
What it means
The failure is on our side. For an authenticated resource POST with an Idempotency-Key, a handled engine-error response is stored and replayed for that key’s 24-hour lifetime. An unhandled exception that interrupts execution releases the reservation, so a retry can run again. The problem type alone does not distinguish these cases.
What to do next
Retry with backoff using the same key. Idempotency-Replayed: true means you received a stored response. Check the resource’s state before considering a new key: the failed operation may have had side effects. If it persists, note the instance path and the time (UTC) and contact support. Check the service status page first if several requests fail together.
Problem body
Every error the API returns is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/engine-error",
"title": "Engine error",
"status": 500,
"instance": "/v1/...",
"docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/engine-error"
}