Am I able to run executions sequentially, instead of in parallel?

This topic was automatically generated from Slack. You can find the original thread here.

Pilgrim Beart : Love the idea of Pipedream. Do you make any guarantee that execution is done in sequence, and not in parallel? For example, if I create a workflow which triggered by posting to a Pipedream URL, and then I do two POSTs to that URL in quick succession, is it guaranteed that the first workflow will complete before the second one starts? The use-case I’m considering is de-duplication. Thanks.

Dylan Sather (Pipedream) : Hi , thanks!

By default, there’s no guarantee on sequential execution, and that’s by design - if you send two HTTP requests to a workflow at the same time, the workflow will run in parallel.

But we’re about to release “advanced delivery” controls that will allow you to serialize executions, apply rate limiting controls, and more. If you’d like a sneak peak at this feature, check out Alpha - Pipedream and check the box for advanced_delivery. Then visit one of your worklow’s Settings and check the radio button next to Limit Concurrency. By default this will serialize executions:

Dylan Sather (Pipedream) : The main thing to be aware of here is, in order for serialization to work, we queue events that are waiting to be executed while your workflow is processing other events. Currently the limit on the number of events that can be kept in that queue is 100. That is, 100 events can arrive and be queued up for serialized execution at any given time.

We’d love any feedback you have! Let me know if you have any questions.

Pilgrim Beart : Thanks - makes a lot of sense

Ruben Nieves : This is an awesome feature

Dylan Sather (Pipedream) : Yeah we’re excited to get it out to everyone! Feel free to test it out and let us know if you have any feedback