Error reference / engine-error
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. The response is HTTP 500.
What it means
Your request was valid; the failure is on our side. Every 500 is counted and reviewed. If the request was a POST with an Idempotency-Key, the key is released so a retry runs the request again rather than replaying a failure.
What to do next
Retry with backoff. If it persists, note the instance path and the time (UTC) and contact support; those two values locate the logged failure. Check the service status page first if several requests fail together.
Problem body
Every error 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://docs.signenvoy.com/errors/engine-error"
}