Paralel / serial execution | Community
Skip to main content
Milan_Vucetic
Milan_Vucetic
Level 9
June 3, 2020
Solved

Paralel / serial execution

  • June 3, 2020
  • 2 replies
  • 3693 views

Hi all,

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.

 

Cheers,

Milan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by _Manoj_Kumar_

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-SubmitNotification.html?hl=submitnotification
https://docs.adobe.com/content/help/en/campaign-classic/technicalresources/api/sm-delivery-QueueNotification.html?hl=submitnotification


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.

https://blog.floriancourgey.com/2018/07/sub-workflow-activity-in-adobe-campaign

 

Let me know if that helps.

2 replies

_Manoj_Kumar_
Community Advisor
_Manoj_Kumar_Community AdvisorAccepted solution
Community Advisor
June 3, 2020

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-SubmitNotification.html?hl=submitnotification
https://docs.adobe.com/content/help/en/campaign-classic/technicalresources/api/sm-delivery-QueueNotification.html?hl=submitnotification


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.

https://blog.floriancourgey.com/2018/07/sub-workflow-activity-in-adobe-campaign

 

Let me know if that helps.

     Manoj     Find me on LinkedIn
Milan_Vucetic
Milan_VuceticAuthor
Level 9
June 4, 2020
Hi @_manoj_kumar_, thanks for the hint. I have redesigned workflow and now have everyting in one JS node (quering, updating and notifying with submitNotification). Adobe does not recommed it for large voulmes as it is developed for maximum of several calls per minute but it will work in my case. Regards, Milan
Raj_Ganta-1
Raj_Ganta-1
Level 5
June 3, 2020

Hi Milan,

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

Terms & ConditionsAccessibility statement

Loading footer...