The two rules that update qTest with results (one Scenario-specific, the other generic) both call the process queue API for results submission status updates. In qTest On-Demand, shared environments may take upwards of several minutes to process queued results. As Pulse rules only run for one minute before timing out ("PULERR001" is thrown) this can leave processing of the API queue unresolved, which is very noticeable with ChatOps integrations.
Expected Behavior
The queue processing API call should be able to continue beyond the normal timeout scope of the rule.
Current Behavior
The two rules that update qTest with results (one Scenario-specific, the other generic) both call the process queue API for results submission status updates. In qTest On-Demand, shared environments may take upwards of several minutes to process queued results. As Pulse rules only run for one minute before timing out ("PULERR001" is thrown) this can leave processing of the API queue unresolved, which is very noticeable with ChatOps integrations.
Expected Behavior
The queue processing API call should be able to continue beyond the normal timeout scope of the rule.
Possible Solution
Add a call to a new rule in UpdateQTestWithResults.js and UpdateQTestAndLinkScenarioRequirements.js that will replicate the queue processing call and resubmit itself until the status ends with "SUCCESS" or "FAILED".
Your Environment