A timer exception in a script task doesnt work

Hi! We have a script taks with a exception flow , we have configured the timer with this:

If the script task delay more than 15 second it has to go in flow exception, but it doesnt

Any option??

Regards,Rebeca

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    now() + intervalds(0, 0, 15) is exactly how I get a timer node to work.  It should work there as well.  If you're fresh out of other ideas, maybe try splitting the process flow and dedicating a timer node to bypassing this when it goes off.

    Now, for explanation of why your original code doesn't work.  All times in Appian are stored as the number of milliseconds since January 1, 2035.  Since that hasn't happened yet, all Appian times we're familiar with are actually stored as negative numbers.  It's actually quite ingenious; as Appian continues to age, the space used to store a date will actually shrink rather than grow like Linux or Mac OS who use Jan 1, 1970. 

    How it's configured in the timer code above is actually 1 equals a day; it does conversions from that before storage.  So the fractional part you established is actually equal to 15 seconds, but it's positive 15 seconds.  15 seconds after the epoch.  Your original code is perfectly configured to go off at exactly 00:00:15 January 1, 2035 and never again afterward.

Reply
  • 0
    Certified Lead Developer

    now() + intervalds(0, 0, 15) is exactly how I get a timer node to work.  It should work there as well.  If you're fresh out of other ideas, maybe try splitting the process flow and dedicating a timer node to bypassing this when it goes off.

    Now, for explanation of why your original code doesn't work.  All times in Appian are stored as the number of milliseconds since January 1, 2035.  Since that hasn't happened yet, all Appian times we're familiar with are actually stored as negative numbers.  It's actually quite ingenious; as Appian continues to age, the space used to store a date will actually shrink rather than grow like Linux or Mac OS who use Jan 1, 1970. 

    How it's configured in the timer code above is actually 1 equals a day; it does conversions from that before storage.  So the fractional part you established is actually equal to 15 seconds, but it's positive 15 seconds.  15 seconds after the epoch.  Your original code is perfectly configured to go off at exactly 00:00:15 January 1, 2035 and never again afterward.

Children
No Data