We have a process model with the start event with the trigger set to a timer. (

If I remember correctly, the process reads the constant value each time it runs - so, if you initially set the constant to 10 am, the process will initially run at 10am. However, if you then change the constant to 11am, the process will next run at 10am (ie not when you're expecting) - but in doing so will read the new constant value, so the run after that will be at 11am.

To summarise - the change in constant value is only actually reflected in the second run of the process after you've changed the constant value. This might explain the behaviour you're seeing where the process appears to ignore changes to the constant's value.

If I remember correctly, the process reads the constant value each time it runs - so, if you initially set the constant to 10 am, the process will initially run at 10am. However, if you then change the constant to 11am, the process will next run at 10am (ie not when you're expecting) - but in doing so will read the new constant value, so the run after that will be at 11am.

To summarise - the change in constant value is only actually reflected in the second run of the process after you've changed the constant value. This might explain the behaviour you're seeing where the process appears to ignore changes to the constant's value.

Hey Phil - thanks for above detail . Is this documented anywhere in Appian documentation ? I am facing similar problem where I changed trigger timer constant from 5 AM PST to 1 AM PST but for first execution its still taking 5 AM PST . Are you saying that for next execution it will take updated trigger timer from constant ? Thanks again for your earlier details

@Phil Bye by do we need to republish process model to take effect of new value 

Publishing process model after constant update worked ., Thanks