- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Workflows - Timer, Event Sources - Timer
- Down Index
- 24of 100
What to do
Check whether you use Pipedream Workflows - Timer, Event Sources - Timer. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 11m it lasted.
Anything that failed between 2023-11-03 21:49 UTC and 2023-11-03 22:00 UTC may need a replay.Subscribe to Pipedream's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pipedream works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Pipedream 3
- investigating
Timer-based triggers — like the Scheduler trigger, and other app-based triggers that run on a schedule — stopped running around 21:30 UTC. Our team is investigating and will post updates here.
provider
- identified
We've reverted the code that introduced the bug. This also only affects v1 workflow triggers, not those using v2 (the latest version of workflows).
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9b0e38e803
Is Pipedream still down?
No, this incident was resolved 2023-11-03 22:00 UTC. For Pipedream's live state, see https://down.guide/pipedream.
How long did it last?
11m, from 2023-11-03 21:49 UTC to 2023-11-03 22:00 UTC, by the times Pipedream posted.
What was affected?
Pipedream named Workflows - Timer, Event Sources - Timer.
What caused it?
Pipedream hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pipedream's official status page, https://status.pipedream.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.