Timed action - stopped working

Duncan_Baxter
Duncan_Baxter
in AppWorks #1

We have recently installed 9.1 SR2 and now find that the 'Timed Actions' from within a process that worked prior to the install have stopped working. The timed action is set to trigger after 1 minute after the process deadline.

 

Any suggestionss welcome?

Tagged:

Comments

  • Jerome_Pearce
    Jerome_Pearce
    #2

    This appears to be an issue introduced with a few others in 9.1.2. The issue we see, which may not be the same as you see, is that loop-back timers fail to fire more than once after entering the stage, even if the time is set in the future again:

     

    http://metastorm.processmapping.com.au/post/Timed-loopback-action-issue-5770520

     

    Given the severity of issues introduced and not yet fixed in 9.1.2, we are still unable to use it or recommend using it. We do hope that QA improves.

  • achopra
    achopra
    #3

    This issue was introduced in 9.1.2, and was fixed in 9.1.2 hotfix 2.  My test solution (which failed in 9.1.2) seems to now work fine once HF2 is applied.

  • Jerome_Pearce
    Jerome_Pearce
    #4

    OK, after re-deploying it does work, sorry.

    The documentation is wrong because it states:

     

    • Redeploy all solutions for the following fix to take effect:

    The tab order does not work as expected when there is a panel inside a panel. (Defect # SR-01272012-0012, DEF19482)

     

    with no mention of needing to redeploy to fix this issue.

  • Duncan_Baxter
    Duncan_Baxter
    #5

    We have applied the latest fix, redeployed the solution but the timed event will not re-trigger.

     

    Any help appreciated?

     

     

  • Tony Wheeler
    Tony Wheeler
    #6

    What variable is your Timed Event dependent upon? A defect was identified that fails to recurse timed loopbacks when using certain variables. This will be fixed in 9.1.3 which is scheduled to be available by the end of the week.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform