n8n - 💡(How to fix) Fix Execution search returns blank list despite Pro license and existing executions [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#29609Fetched 2026-05-02 05:46:32
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question What is the error message (if any)? No error message — just a blank execution list when any search term is entered.

RAW_BUFFERClick to expand / collapse

Describe the problem/error/question When searching executions using the search/filter functionality, the results list returns completely blank — no executions are shown. This happens even though executions clearly exist and are visible when browsing without a search filter. The search feature is supposed to be available on Pro and above licenses. What is the error message (if any)? No error message — just a blank execution list when any search term is entered. Please share your workflow/screenshots/recording Steps to reproduce:

Go to any workflow's Executions tab Enter any search term in the search box Execution list goes blank — no results returned Remove the search term — executions reappear normally

Share the output returned by the last node N/A — the issue is in the executions UI, not within a workflow. Debug info

n8nVersion: 2.17.5 platform: docker (cloud) nodeJsVersion: 24.14.1 nodeEnv: production database: sqlite executionMode: regular concurrency: 50 license: enterprise (sandbox) pruning: enabled, maxAge 720 hours, maxCount 25000 userAgent: Chrome 147 / macOS

Expected behavior Searching executions should return matching results filtered by the search term. Actual behavior Search returns a completely blank list every time regardless of search term used.

extent analysis

TL;DR

The issue might be related to the search functionality in the executions UI, and checking the search query or filtering logic could help resolve the blank results.

Guidance

  • Verify that the search term is correctly passed to the backend and that the filtering logic is applied as expected.
  • Check if the issue persists when using different search terms or when searching for executions with specific attributes (e.g., status, date).
  • Investigate if the problem is specific to the Enterprise license or if it occurs with other licenses as well.
  • Review the database (sqlite) to ensure that the execution data is correctly stored and can be queried.

Example

No code snippet can be provided without more information about the search functionality implementation.

Notes

The issue might be related to the specific version of n8n (2.17.5) or the docker environment, but without more information, it's difficult to determine the root cause.

Recommendation

Apply workaround: Try to reproduce the issue with a different license type (if possible) to determine if the problem is license-specific, and check the search query and filtering logic to ensure they are working as expected.

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 Execution search returns blank list despite Pro license and existing executions [1 comments, 2 participants]