I’m experiencing a recurring issue that has persisted for years regarding scenario executions getting stuck in infinite processing states.
The problem occurs when using DeepSeek AI - occasionally the module becomes “stuck” and processes indefinitely. This forces me to wait up to 45 minutes (the duration of my plan’s execution limit) for the scenario to time out on its own, as there’s no way to manually stop specific executions.
During these episodes:
-
I can see the scenario is running, but cannot stop it
-
I cannot run new tests because the scenario shows as “in execution”
-
There are no controls to terminate specific runs
-
I’ve previously experienced significant operation consumption due to unstoppable loops
While I appreciate Make’s clean interface, the lack of execution management features like a “Stop” button for individual runs or preventive safeguards has been a long-standing concern.
Is there any solution or workaround for this issue? I’d appreciate guidance on how to handle these situations when they occur.
Thank you for your assistance.
