Skip to content
Upstash · Data and observabilityFeb 6, 2025, 10:10 UTC

QStash Workflow Run Failure

InformationalDeploymentUpdated 19h ago
Feb 6, 10:10 UTCFeb 6, 10:10 UTC
Duration
0m
Impact
Informational
Root cause
Deployment
Upstash, 90 days
5 incidents
Affected
Not listed by the vendor.
Status page

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

  1. 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 history

Also caused by deployment or rollout

All
StartedIncidentDuration
Sep 1106:22 UTCIssues with Workers VPC hostname route resolution on 2026-09-11Cloudflare0m
Aug 2014:43 UTCIntermittent failures creating agent tasksGitHub9h 54m
Aug 2000:31 UTC[Medium] Issue with Microsoft Office Integration and Box EditBox1h 13m
Aug 622:22 UTCTrouble Using Search Bar For Some AdminsSlack2h 44m
Jul 2110:23 UTCJob runs failing at the git clone stepdbt Labs2h 29m
Jul 1907:33 UTCSome EMEA customers experiencing Git clone failures (403 errors) on thier accountsdbt Labs6h 22m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.