I am using the Pipedrive update trigger and it often sends two triggers quite quickly.
Is there a way to serially process trigger events or, only allow 1 instance of a trigger node to run at once?
I dont mind backing these events up serially, its just a problem when they are running concurrently.
It looks like your topic is missing some important information. Could you provide the following if applicable.
This could for example be achieved by using a message broker like RabbitMQ. You’d still receive all trigger events as they are sent from Pipedrive but instead of processing them directly add them to the queue in your Pipedrive workflow.
Then have a second workflow consuming this queue through the RabbitMQ Trigger node which allows you to configure the Parallel Message Processing Limit option ensuring only one execution takes place at once:
That is a good solution, thank you for recommending it!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
