Skip to main content
mollyn6512
mollyn6512
January 12, 2023
Question

Timer Event node configured with Scheduled Delay is cancelled when running the process

  • January 12, 2023
  • 9 replies
  • 1 view

Hi everyone, 

One of the process models that I'm working on is using a Timer Event node, which is having a scheduled delay setting as shown below: (the constant returns 2 (integer))

I think the node supposes to delay for 2 minutes, then will activate the next node (Merge document) to run. 

However, this Delay node has stuck there for much longer than 2 minutes, and when I check Process History, the node is Cancel. 

The Merge Document node does not have any setting for Scheduling either

I haven't worked with Timer Event before, and couldn't find the reason for this behaviour from documentation. Could anyone help me with this?

Thanks a lot,

    9 replies

    S
    sathvikb8954
    January 12, 2023

    Hi [mention:b18d9a2f367a407ca0cf8a9b71bef972:e9ed411860ed4f2ba0265705b8793d05],

    So when you assign a timer event node after the given time ex:- 2min try to press refresh icon, by refreshing the process model while debugging it goes to the next node.

    Hope this is helpful

    mollyn6512
    mollyn6512Author
    January 12, 2023

    I refreshed but it did not go to the next node...

    J
    josec0007
    January 12, 2023

    Is this process running sync or async? If it's running sync the parent process might be completing it if you have an end node with terminate process.
    Does this gets cancelled when you run it as debug mode? 

    I haven't used constants for timers but what I have been using is the option the date and time specified by this expression I'm using 
    =now() + intervalds(0,0,10)/*Wait 10 seconds*/

    mollyn6512
    mollyn6512Author
    January 12, 2023

    This process run synchronously, but the Merge Document node needs to be executed to pass the output to the parent process. 

    Currently the parent process was still able to continue as the process still hit end node despite the cancelled Timer Event, but the output from this sub-process is left blank. 

    mollyn6512
    mollyn6512Author
    January 12, 2023

    Also, I run the whole workflow, and realised I couldn't see the data returned to parent process, and found out it was because of the delay node

    konduruc733182
    konduruc733182
    January 12, 2023

    Hello mollyn6512,

    Can you check the constant that you are passing as reference. What values does it have, i mean the type of values. and if it is array can you confirm if you have passed the index of the integer/value.

    If all is well then try wrapping the constant with tointeger() in the expression for the  scheduled delay

    csteward
    csteward
    January 12, 2023

    We also need to know what is in the configuration under the Advanced Options:

    This is used to define any conditions which can prevent the timer from firing, say if you have a boolean expression which is returning false(), the timer will not fire no matter the time delay setting.

    From there, as the others have mentioned, the timer ends up becoming Cancelled as the parent process completes prior without this node ever having been completed.

    Terms & ConditionsAccessibility statement