Hey guys,
I’m encountering an issue with a process I built using the REFramework. When debugging in the Studio, clicking ‘Stop’ causes the process mark the transaction as ‘Successful’ instead of keeping it as ‘In Progress’ as it should. As you can see, I stopped the job in the middle of a workflow (part of the Process in the Framework), but the bot thinks the case is complete.
This issue occurs consistently across many transactions.
What could be the reason for this?
Thanks!
When you hit stop it depends on what activity you hit stop as well…it would compelte and then stop
Also yes we see this intermittent happening only in debug mode and would not occur for you in actual runs
Cheers
Hey! Thanks for your response
Is there a way to prevent it? I dont like having to clone the queueItem each time I debug
Probable cause would be this:
If the execution is in the Try or Catch block when the Kill command is received by the Robot, it first tries to Cancel the process, skipping to the Finally block. If the logic inside the Finally block is not finished in three seconds since receiving the Cancel command, the whole execution is killed and the overall process is successful in the logs as no errors were recorded in the Catch block since it was skipped.
(Robot - Stopping a Process)
So, if you are setting the transaction status in a Finally block, that code has 3 seconds to run after you click on the Stop button in Studio. This would also happen if you Kill if from Orchestrator (but not when soft-stopping).
My STS is inside a Finally. I guess I could solve it by adding a Boolean flag so the Transaction Status is modified to “Successful” only if this flag is True
That’s an intermittent thing…If you are careful not to hit either by adding break point or so it would help
cheers
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.