n8n - 💡(How to fix) Fix Only 24hs of executions avaliable [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28476Fetched 2026-04-15 06:44:21
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
closed ×1commented ×1labeled ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

I am accessing the executions, but there are only 24hs of executions avaliable

What is the error message (if any)?

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.13.3
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 50
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36 edg/146.0.0.0
  • isTouchDevice: false

Generated at: 2026-04-14T12:57:33.428Z

extent analysis

TL;DR

The issue is likely due to the pruning configuration, which limits the maximum age of executions to 720 hours, causing older executions to be deleted.

Guidance

  • Check the pruning configuration to understand the current settings: pruning.enabled is true, pruning.maxAge is 720 hours, and pruning.maxCount is 25000 executions.
  • Verify that the executions are being pruned by checking the database or storage for any signs of deleted executions.
  • Consider increasing the pruning.maxAge value or adjusting the pruning.maxCount to retain more executions.
  • Review the workflow and execution patterns to determine if there are any other factors contributing to the limited availability of executions.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The pruning configuration is enabled, which means that executions older than 720 hours will be automatically deleted. This could be the cause of the limited availability of executions. However, without more information about the workflow and execution patterns, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Increase the pruning.maxAge value to retain more executions, as the current setting may be too restrictive.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Only 24hs of executions avaliable [1 comments, 2 participants]