we have one old workflow which receives a parameter, query recipients table, update one flag and send notification via continuous delivery. Recently, there were around 400 simultaneous invokes with different parameter and we noticed that AC waiting to query all 400 recipients and update flag and then send notification. This causing a big delay in notifying customers.
Any idea how to ensure that process query first recipient, update flag, send notification and then start again with new recipient? I am open for ideas how to completely redesign this workflow based on your good practice.
Hello @Milan_Vucetic ,
In case you are triggering this external signal from a webApp. You can directly update the recipient schema from an API call and then trigger the email via nms.delivery.QueueNotification or submitNotification functions via JS.
Documentation available here https://docs.adobe.com/content/help/en/campaign-classic/technicalresources/api/sm-delivery-SubmitNot...
If you are triggering this from another workflow then you can go for a sub-workflow which will update the data and then trigger an email.
Let me know if that helps.
I think the external signal invoking is asynchronous and that will probably result in triggering the workflow again and again even before it is completed.
Think of a solution to handle that.I am not aware of what exactly you are trying to do there, so cant really comment.
you can use session write and later run the workflow every one or two minutes to send notification