Incidentsby GlyphQStash Workflow Run Failure
Feb 6, 10:10 UTCFeb 6, 10:10 UTC
Duration
0m
Impact
Informational
Root cause
Deployment
Upstash, 90 days
4 incidents
Affected
Not listed by the vendor.
Final update
Latest QStash release caused some Workflow runs to fail due to a bug in Workflow URL detection mechanism. Affected workflows did not start at all and moved directly to DLQ. These workflow runs, which show "detected non-workflow destination" message in the response body, can be retried from DLQ. This was a partial failure, lasted from 10:10 to 11:00 UTC, not all users' workflows were affected.
Timeline
- Resolved · Feb 6, 10:10 UTC
Latest QStash release caused some Workflow runs to fail due to a bug in Workflow URL detection mechanism. Affected workflows did not start at all and moved directly to DLQ. These workflow runs, which show "detected non-workflow destination" message in the response body, can be retried from DLQ. This was a partial failure, lasted from 10:10 to 11:00 UTC, not all users' workflows were affected.
More from Upstash
Full historyBrief connection proxy degradation in us-east-1lasted 0mIntermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)lasted 0mUpstash Console login issuelasted 0mMessage Persistence Issue , QStash us-east-1lasted 0mFly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Regionlasted 1h 15mQStash us-east-1 - URL Publish Errorslasted 0m