Avoiding 'Scenario Rejected' Error on Make.com: A Guide

Have you ever encountered the error message 'Scenario was rejected: Scenario is running' while using Make.com? This error can be quite frustrating, especially when it leads to unnecessary operations and wastage of OpenAI API usage. But don't worry, we've got you covered. In this blog post, we'll walk you through the problem and its solution.

The Problem

The error 'Scenario was rejected: Scenario is running' typically occurs when you're trying to run a scenario that's already running. This can happen if you're using the Repeater module incorrectly, leading to the output of many bundles. The scenario continues to run, and you can't stop it, leading to a waste of resources.

The Solution

The solution to this problem is quite simple. First, you need to save your scenario before scheduling it. This is because once it's scheduled, it will run automatically for the first time. If you're working with a repeater module, it can cause a loop until the limit is exceeded. Since scenarios can't be halted, it's wise to save your work before attempting such intricate tasks.

Troubleshooting Tips

If you're still facing the problem, try reloading the entire page. If the problem persists, revisit your actions leading up to the situation. Sometimes, the problem could be a minor error on your part. Refrain from engaging in practices that could lead to such issues.

Conclusion

In conclusion, the error 'Scenario was rejected: Scenario is running' can be avoided by saving your scenario before scheduling it. Remember, once a scenario is scheduled, it will run automatically for the first time. So, be careful when working with modules that can cause loops, like the Repeater module. We hope this blog post has been helpful. Happy Making!

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.