I am trying to run this scenario once but getting error in log
Scenario was rejected: Scenario is running
I was checking history and I saw that the scenario is running how do it stop that process?
LOG
History tab
I am trying to run this scenario once but getting error in log
Scenario was rejected: Scenario is running
I was checking history and I saw that the scenario is running how do it stop that process?
LOG
History tab
I found history list and could see that the scenario running and cannot stop. It caused unnecessary operations and waste of OpenAI API usage. How to stop this scenario from running?
After waiting for almost 27mins the task got completed. How to avoid such error in future?
I’m not sure if you are using the Repeater module correctly. I’ve never seen the OAI module output that many bundles before.
This seems like a complex scenario you’re trying to make, perhaps exporting the blueprint might help others investigate further and answer your question.
At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
Uploading it here will look like this:
blueprint.json (119.3 KB)
I believe there was problem with the repeater module. The situation became unchanging, and my attempt to reload the entire page led to facing this problem. After one cycle was finished, the situation has now resolved and the scenario is functioning correctly, as intended.
I faced the same problem once more, but this time I revisited my actions leading up to the situation. I realized that the problem was actually a minor error on my part.
To prevent such issues, it’s advisable to refrain from engaging in such practices.
Solution:
A recommended approach is to save your scenario prior to scheduling it. This is because once it’s scheduled, it will run automatically for the first time. In my case, I was working with a repeater module that ended up causing a loop until the limit was exceeded. Since scenarios can’t be halted, it’s wise to save your work before attempting such intricate tasks.
Heya @M.Jasani
I just wanted to quickly jump in and say awesome work figuring this one out on your own!
Also, thank you very much for getting back to the community and sharing what you learned with us. We truly appreciate that you kept us in mind and marked the problem as solved so that other users can easily find it when looking for similar information