A workflow is stuck or slow

Waiting is not failing

Workflows are durable: a step that is waiting on an external system stays waiting rather than failing. Open the run and look at the current step before assuming something is broken.

Common reasons a step waits

It is waiting on a rate limited system, on a sync that has not finished, or on an approval nobody has given yet.

A step that failed

A failed step names the error it received. Retry it once the cause is fixed; the run resumes from that step rather than starting over.

Everything is slow

Check whether a large first sync is running in the same workspace. Syncs and workflows share the same usage budget, so a big backfill can slow everything else until it finishes.