Does '2.5k workflow executions' in Cloud Pricing Refer to Daily or Monthly Limits?

Below is some clarification regarding what the "2.5k workflow executions" means on n8n Cloud:

Execution Data vs. Execution Count

In n8n Cloud pricing, a reference such as “2.5k workflow executions” isn’t a cap on how many times your workflows can run (the executions themselves keep running and are processed) but rather relates to how many execution logs are retained in your instance’s history.

For example, on some plans (like the Start or Starter plans) n8n retains up to 2,500 execution records at any given time with a log retention period of 7 days. If your workflows run more frequently than this, older execution logs will be pruned (removed) automatically once those limits are reached.

What This Means for Your Use Case

Since you mentioned that your workflow trigger runs every minute—totaling roughly 1,440 executions per day—you would indeed exceed the 2,500 stored logs in a month. However, this does not mean your workflows are blocked. Instead, the system simply only saves information from the most recent executions (up to 2.5k) for you to review in the UI.

Summary

• "2.5k workflow executions" in this context refers to the number of execution logs (historical records) that n8n Cloud retains, not a cap on actual workflow runs.
• The retention period is typically 7 days for the Start and Starter plans.
• Your workflow will run as expected even if it’s triggered each minute, although older execution records will be pruned automatically once they exceed the 2.5k limit.

If you have further questions about managing execution data or other aspects of n8n Cloud, feel free to ask!