Needs to avoid same ticket being processed at the same time to prevent overwriting

What are you trying to achieve?

I have a scenario that is triggered by a webhook that gets all the incoming tickets as soon as they arrive and follows through the scenario until the final module which is to add a tag along with the existing tags. The problem is I have 2 different scenarios with the same logic and if their trigger catches the same ticket at the same time, one of the tags added get overwritten

Welcome to the Make community!

Turn on “Sequential processing” in your scenario settings.

For more information, see the Scenario settings page in the Make Help Centre, which covers the following:

  • Sequential processing
  • Data is confidential
  • Allow storing of incomplete executions
  • Enable data loss
  • Auto commit
  • Commit trigger last
  • Max number of cycles
  • Number of consecutive errors

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Hey there,

could you please share why you have two scenarios watch the same webhook? What is the difference between them and what parts are the same so it results in tags getting overwritten?

I believe the best approach here is to have one scenario watch the webhook and then call different scenarios to continue the execution when different things need to happen so there is no conflict between scenarios.