This topic was automatically generated from Slack. You can find the original thread here.
Is there a way to pause a workflow or delete a workflow queue that was started in error and will runs for hours if not stopped?
Currently, there is no built-in way to pause a running workflow in Pipedream. However, you can manually cancel a workflow execution if it’s in a retry state due to an error. When a step throws an error and is set to retry, it exports an $attempt object with a cancel_url property. You can call this URL to cancel the retry. Keep in mind that this method is only applicable when a workflow is in a retry state due to an error. For more information on error handling and retries, please refer to the Pipedream documentation: Settings If you need further assistance or want to discuss your specific use case, feel free to visit https://pipedream.com/support. Pipedream offers a range of community support options, and advanced customers get access to email and community support. Business customers get a dedicated account rep and a Slack channel with the Pipedream team.
I forgot to deploy a workflow that was temporarily set up to send collections to my processing workflow instead of individual products so its now sent the same 119 item collection to the processing workflow 9 times for the 9 times it was triggered by an individual product. 1000 invocations + 3 hours 
EMERGENCY STOP button might be a feature worth adding? It could have been MUCH worse! It could easily have been a 2000 item collection triggered multiple times.
If you visit your workflow settings, you can disable your workflow completely there. I need to follow up to see how the error / retry queue is impacted by pausing a workflow — I’m actually not sure if we’ll clear the queue or pause.
I’ll try it. Thanks. I do want to use the workflow. I just need to clear the queue to do so. So I’ll try disable-reenable and see what it does.
Does “delete all” delete the queue items or the queue items display?
That just deletes all the items you see in the display list, it doesn’t affect the queue.
Disable-Reenable did the trick! Thanks! Saved a bunch of time!
We’ll document so Mario knows, too!