Skip to main content
July 9, 2021
Question

Timer problems in the start node

  • July 9, 2021
  • 4 replies
  • 0 views

Good afternoon,

 We are consuming an external process that has a start timer configured as follows:

The rule! Delay has this code

if(

  totime(now()) < cons!START_TIME,

  datetime(

    year(today()),

    month(today()),

    day(today()),

    hour(cons!START_TIME),

    minute(cons!START_TIME)

  ),

  datetime(

    year(today()+1),

    month(today()+1),

    day(today()+1),

    hour(cons!START_TIME),

    minute(cons!START_TIME)

  )

)

The value of the constant is:

The configuration of the user who starts the process is

And the process has the overwrite option checked

The problem we are having is that the process is running at 2:00 AM instead of 1:00 AM as we have in the configuration.

Can you think of why this could be happening?


A greeting and thanks in advance

    4 replies

    stefanhelzle0001
    Brainy
    July 9, 2021

    Could it be that the user publishing the model has a different time zone configure?

    July 9, 2021

    Hi Stefan,


    In this case, the person who is executing the process is the one who published it the last time and has the one I mentioned in its configuration.

    csteward
    July 9, 2021

    Another thought is that, has the start time constant changed from 2 AM to 1 AM since the process model was last published?  As updating a constant that drives this start time recurrence will not take effect until the process model is re-published.  

    July 12, 2021

    Hello Chris,

    I have reviewed and that is not the case, the constant was modified before publishing the process. Also before it had another value other than 2:00 AM.

    Greetings and thank you