Hi everyone, Jonathan here from the product team.
We recently discovered an issue with insights data that has been affecting users running n8n with queue mode (using one or more workers) that we wanted to give you a heads up about what has happened and how it might impact you.
The Issue
If you’ve been running queue mode on version v1.100.0 or later (released end of June 2025), your insights will likely have been showing inflated execution counts. During this period, executions were essentially being reported twice. Once from the main instance and once from a worker, resulting in roughly double the number of executions appearing in insights. The exact impact varies depending on factors like when you enabled queue mode or if there were periods at all that queue mode was inactive.
Fixing this issue
We have a fix ready for v1.122.0, which will be available from Monday (24th November). This fix only applies to data going forward as we cannot accurately correct historical insights data that has already been collected.
This means that once you upgrade to v1.122.0, your data for your insights banner/dashboard will return to normal, correct levels. However, after this upgrade, the execution counts in your insights will appear to drop when compared to previous periods. In reality, nothing will have changed in your workflow execution activity, with the new numbers simply returning to the correct data. Historical data will remain inflated, so any comparison to periods after upgrading to v1.122.0 will show higher volumes than current data.
Who does this impact
This issue only affects instances running in queue mode on v1.100.0 or above. This includes self-hosted instances and Enterprise cloud accounts. Cloud users on Starter and Pro plans are not impacted.
Important: No Billing Impact
This issue only affects how the insights feature displays execution data. For those on an execution-based pricing plan, your billing and execution quotas are completely unaffected. Execution counts for billing are calculated separately from insights and have always been accurate.
Finally, I want to apologise for any confusion or inconvenience this has/will cause. I know many of you rely on insights data to monitor usage and measure the impact of your workflows, and this clearly isn’t ideal. We have learned from this and will be putting changes in place to ensure this doesn’t happen again going forward.
If you have any questions about this issue, please feel free to respond on this thread and I’ll be happy to help clarify anything that I can.