Clarification on Wait Activity Behavior in Daily Running Workflow | Community
Skip to main content
W
WarisaraYi
September 10, 2024
Solved

Clarification on Wait Activity Behavior in Daily Running Workflow

  • September 10, 2024
  • 3 replies
  • 815 views

Hi all,

 

I have a workflow that runs every day and includes multiple Wait activities, each lasting more than one day. My question is: when the workflow runs again the following day, will the ongoing Wait activities be terminated, or will they continue until their specified wait time has been completed?

Thank you in advance for any clarification!

 

Best regards,

Warisara

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 DavidKangni

@warisarayi 

If the same branch of a workflow has several schedulers/wait, the number of tasks to be executed will be multiplied exponentially, which would considerably overload the database.

basically, if the scheduler resumes before you wait the next activities won’t move forward.

 

ACC is using temporary tables which are deleted after every run.

 

Thanks,

David 

3 replies

S
SorenDP
Level 4
September 10, 2024

To my knowledge, the wait activity has its own logic so to speak. 

Meaning, whenever subjects enter the activity, those subjects will wait fo rthe specified time regardless of the schedule activity beforehand. So the short answer following this logic is: It will always wait for the specified time and not force-execute. 

This is however pretty straightforward to test yourself, so I would recommend just testing that behavior to confirm 🙂  

    DavidKangni
    Community Advisor
    DavidKangniCommunity AdvisorAccepted solution
    Community Advisor
    September 10, 2024

    @warisarayi 

    If the same branch of a workflow has several schedulers/wait, the number of tasks to be executed will be multiplied exponentially, which would considerably overload the database.

    basically, if the scheduler resumes before you wait the next activities won’t move forward.

     

    ACC is using temporary tables which are deleted after every run.

     

    Thanks,

    David 

    David Kangni
      harikrishnadevanabowina
      harikrishnadevanabowina
      Level 4
      September 13, 2024

      Hi @warisarayi  It is suggested to use the 'wait' activity -  use sparingly and only when necessary to achieve specific workflow goals. A bit strange to think how you are managing the workflows which are lasting more than a day. May be it is time to optimize, break them in to significant segmented data queries,

       

      But coming to your question: The Wait Activity will affect the workflow's completion time within the daily cycle. If the Wait Activity's duration is significant, it might push the workflow's completion beyond the intended daily execution window.

       

      BR, Hari Krishna D

        Terms & ConditionsAccessibility statement

        Loading footer...