-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading large execution history runs fail #12234
Comments
Hey @nirkons Do any errors appear in either the browser console or in the n8n logs? |
1 similar comment
Hey @nirkons Do any errors appear in either the browser console or in the n8n logs? |
In the docker logs I didn't see anything, do I need to set any parameter in the docker compose to see debug logs? The console I didn't check, I'll check and update |
index-fCEqBD8K.js:14301 this is the only thing in the console, nothing in the docker logs, but im unsure if i need to increase debugging in docker? thanks |
Hi @nirkons, Could you please clear the browser's cache data? Thanks |
Bug Description
On flows that are dealing with files and have failed, when trying to view the run, it loads for a while, then the error shows up:
All settings are set to save:
To Reproduce
Create an example flow:
make the flow fail to run.
try to view the execution
Expected behavior
the failed run can be displayed in the execution log
Operating System
ubuntu 22.04
4 dedicated VCPU, 16GB RAM, 8GB swap
n8n Version
1.72.1
Node.js Version
docker
Database
PostgreSQL
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: