Hi Dojo,
I have a self written protocol where this issue shows up.
But inside I don’t see any issues here, the protocol is working fine.
Problem is maybe that the QAction is running really long, in my test here it was running for over 20mins.
The time is fully okay because there are a lot of Thread.Sleep inside.
Any ideas that the error is not showing up?
Hi Stefan,
The warning that you are seeing is generated by the SLWatchdog process.
Your protocol most likely has some group that is being executed that contains your QAction (correct me if this is not the case).
The SLWatchdog process expects a group to not execute longer than 15 minutes, or otherwise will assume that the group is stuck processing (what we call an RTE: Run-Time Error).
More information can be found here: https://docs.dataminer.services/develop/devguide/Connector/Troubleshooting/Use_cases/Protocol_thread_run_time_errors_use_cases.html#open
This is correctly flagged, as this long-running group is blocking everything else that needs to happen, even for example button presses.
If you expect this QAction to run this long, you can find more information in the answer of the following DOJO post: https://community.dataminer.services/question/a-way-to-suppress-thread-problem-rte-for-actions-that-take-longer-than-15-minutes/
Note: if your long running QAction exists out of a lot of small steps, it is advised to split the big QAction into multiple QActions that each execute a part of the logic. These can be put separately on the SLprotocol execution thread. More information about the execution can be found here: https://docs.dataminer.services/develop/devguide/Connector/InnerWorkingsSLProtocol.html#main-protocol-execution-thread
Kind regards,
Thanks Bram, excellent answer!