All executions appearing as failed on 0.221.0

[MeesJ]

Describe the bug
After I upgraded my n8n instance to 0.221.0, all executions are appearing as failed in the list with all executions, even though in reality the executions did not fail.

To Reproduce
Steps to reproduce the behavior:

1. Go to the homepage of your n8n instance
2. Go to the executions tab (all executions)

Expected behavior
I expect the list of executions to show the actual status of executions, instead of letting all executions appear as failed.

Environment (please complete the following information):

• OS: Ubuntu 22.04 LTS
• n8n Version 0.221.0
• Node.js Version [e.g. 16.17.0]
• Database system MariaDB
• Operation mode Main

Additional context

[Joffcom]

Hey @MeesJ

Is this the same as #5765?

Quick edit... just noticed you commented on that as well. Are your workflows webhook based as the trigger or a mix of schedule and webhook?

[MeesJ]

Is this the same as #5765?

Partially. The errors that OP showed in his issue do not appear on my side, but I do have the issue with executions appearing as failed. This not only affects workflows with webhooks, but also workflows that use HTTP request nodes. No errors appear in the logs though. I was instructed to create a new issue by @netroy.

Are your workflows webhook based as the trigger or a mix of schedule and webhook?

Webhook based as the trigger. Not a mix of schedule and webhook.

[mzayn]

i have same issue on this. got error on webhook, also fail workflow backup to github

[netroy]

if either of you are running n8n via docker or docker-compose, can you please share docker command or the compose file to help us reproduce this?

We are able to reproduce this and looking into it now.

[MeesJ]

Thanks for the swift resolution @netroy and the rest of your team!

[janober]

Fix got released with [email protected]