I need to limit the number of times a scenario can execute per month to prevent overuse by my clients. Ideally, once the scenario hits a certain limit (e.g., 1000 runs), it should stop executing until the next billing cycle.
I’m looking for the best way to:
Enforce a strict monthly cap on executions.
Automatically reset the count at the start of each month.
Ensure the scenario stops cleanly once the limit is reached (without unnecessary executions burning operations).
Would love to hear if anyone has a way to handle this!
It is possible but not efficient to do it within a scenario. This is because it requires one additional operation per scenario run to get the number of operations used for that scenario, and two additional operations to start/stop the scenario.
But if you want to do it, it’s possible
Example
Here is an example of how your scenario could look:
This is just an example. Your final solution may or may not look like this depending on your requirements and actual input data.
