Extra delay required for Execute transition (delayed execution) post function

Issue #811 resolved
Weston Rossborough created an issue

Hi Fidel,

I'm having an issue where I need to include a 1000 ms delay to my post functions that execute a delayed transition. In the system logs I'm finding this error.

2017-09-25 14:18:30,693 Timer-9 DEBUG Weston_Rossborough@URMC.Rochester.edu 858x10248x1 pijdl3 172.17.3.4 /secure/CreateIssueDetails.jspa [c.f.j.p.workflowToolbox.shared.IssueTransitionManager] *** TRANSITION "Approved" ON ISSUE RSSD-148 AT STATUS "Awaiting manager approval", CAN'T BE EXECUTED DUE TO CONDITION NOT SATISFIED. DETAILS: It seems that you have tried to perform a workflow operation (Approved) that is not valid for the current state of this issue (RSSD-148). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.

I've noticed this on a few workflows that use this type of post function. Extending the initial delay from 500 ms - 1000 seems to fix it.

My big question here is why this is suddenly required? I think something is hanging up the post function in the background requiring the addition delay time.

Here is the post function referenced in the above error.

DelayedTransition.jpg

Any assistance with diagnosing this would be much appreciated.

Thanks, Weston

Comments (2)

  1. Fidel Castro Armario repo owner

    Hi @WestonR,

    Can you, please, attach a screenshot of conditions and validations tab in transition Approved?

    It's probably caused by a condition not being satisfied due to a previous transition execution that requires some time after transition execution to fully set the issue. The problem appears after some modification in your JIRA instance that is making the transition to require a longer time to set the issue. Typical causes are:

    • You have updated to a new version of JIRA that runs slower than previous one in your same server.
    • Your server is running new processes that are consuming more resources making JIRA run slower.
    • Some resources in your server have been reduced making JIRA run slower.
    • You have migrated your JIRA instance to a slower server.
  2. Weston Rossborough reporter

    Hi Fidel,

    Thanks for responding. I was actually able to fix this with a full restart of the server. I'll close this ticket.

    Thanks Weston

  3. Log in to comment