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
Workflow Execution Issue in n8n Version 1.21.1 #8217
Comments
Hi @Caretek1, You said: "I believe this could be a bug introduced in the latest version and thought it crucial to bring it to your attention for further investigation" and what is the bug? |
Hey @Caretek1, Thanks for the report, I have just checked on the 2 releases we did recently (1.23.0 and 1.22.4) and I am not able to reproduce this. If your workflows are using scheduled triggers can you try updating to |
I have a self host container through cloudron and they dont provide pre releases so once they provide us 1.22.4 i will check. I reverted back to previous version |
Hey @Caretek1, Have Cloudron updated their side yet? |
@Joffcom yes, it's been updated from Cloudron side. |
@Joffcom sure! We track the releases at https://github.com/n8n-io/n8n/releases . We have our own Dockerfile since we have some restrictions on how the app is packages (for example, we deploy containers as readonly filesystem) . The package code is at https://git.cloudron.io/cloudron/n8n-app . We have made over 200 package releases, thanks for the great app! |
Hi I confirmed the issue is resolved with 1.22.4 |
Dear n8n GitHub Team,
I am writing to report a critical issue we've encountered with n8n following an update to version 1.21.1. This issue affects the workflow execution functionality and is consistent across multiple instances running in Docker containers.
Self Hosted through Cloudron
Issue Details:
Version Affected: 1.21.1
Symptom: Both automatic and manual workflow executions fail to run post-update.
Environment: The issue has been observed in 4 separate n8n instances running as Docker containers.
After updating to version 1.21.1, we noticed that neither automatic nor manual workflow executions were functioning as expected. This was consistent across all our instances. To confirm that the issue was specific to the update, we reverted back to the previous version of n8n. Post-reversion, the workflow executions returned to normal functionality.
I believe this could be a bug introduced in the latest version and thought it crucial to bring it to your attention for further investigation. If there are any additional details or diagnostic information you require, I am happy to provide them.
Thank you for your attention to this matter. We rely heavily on n8n for our workflow automations and are keen to update to the latest version once this issue is resolved.
Best regards,
The text was updated successfully, but these errors were encountered: