So i’ve been using n8n fine for a few weeks. Over the past couple days I started getting some error messages when saving workflows or trying to activate workflows. When I try to activate workflows I sometimes get the following error. [Screenshot 2022-11-10 at 7.57.17 AM] When trying to save a wo…

Hi @dejecj , we released a new n8n version 0.202.1 yesterday including a fix for workflow activation. fix(editor): Fix workflow activation from the Workflows view n8n-io:master ← n8n-io:N8N-5430-workflow-activator-fix ope…

Hi @dejecj The first one I have never seen. The second I have seen when opening a workflow in 2 tabs, since the new UI it seems to be less permissive when saving. Luckily we can copy the whole workflow refresh the page and paste it back in. It can be annoying though.

@BramKn Well that was my thought on the on the second one. Which is why while troubleshooting I closed every browser window except the n8n editor and was still getting the error for some reason. I also think the errors might actually be related. I just tried again after restarting. I am able to save…

Yeah the closing of tabs wont work. it holds the workflow somewhere even after closing all other workflows I think. We will see what the n8n team has to say about it. :slight_smile: Please fill in the setup information template, though. As it will help them find the issue.

Hello, we encounter the same error message “No entity column hash was found”, and cannot activate our workflow. Thank you for your help ! Installation : docker-compose with n8n version 0.201.0

I also got this No entity column hash was found error. The workflow could be saved correctly. I managed to find out that the webhook node that i have in this workflow, used the same endpoint as other workflows. At the moment i changed the webhook endpoint url, the “hash” error message disappeared an…

Hey all, while you can try with the new update for sure, I am not sure it will solve the original problem which looks to me requires a DB migration. The error message says that the hash column is missing and that is something we added recently, so I guess DB schema has to be updated but I don’t hav…

@milorad @marcus Thanks. I ended up doing both of the suggested steps. I basically deleted my n8n instance database and all (after exporting my workflows). Then started from scratch with version 0.202.1. I have not seen the errors since. It was definitely a pain getting all my workflows back in and …

hi, I have been testing on 0.202.1 before i raised this issue, so it is not fixes by this release

We have updated to 0.202.1. At first I was not able to activate the impacted workflow. But after I deleted the trigger node, and re-created it (without modifying other nodes of the workflow), I was able to activate it. My workflow is working again. Thank you @marcus @milorad !

Arf, the error is coming back again. It re-appeared after I added the webhook-test-url to Gitlab manually (webhook url for production were added automatically to Gitlab)

Workflow could not be activated

Questions

marcus 11 نوفمبر 2022، 11:56ص 7

Hi @dejecj,
we released a new n8n version 0.202.1 yesterday including a fix for workflow activation.

@tpatulacci @sl-tobe
Could you upgrade your n8n instance to 0.202.1 to see if this fixed your issue.

الموضوع		الردود	مرات العرض
No entity column "hash" was found with Zendesk Node Questions cloud , trigger , zendesk	9	1011	29 نوفمبر 2022
Workflow could not be activated: Unknown error Questions core	3	1087	12 يناير 2023
Imported workflows are not activated even after calling the activate=true in cli Questions workflow-settings	5	673	5 أكتوبر 2023
All workflows deactivated Questions	18	1025	9 يوليو 2024
Error when trying to activate specific workflow Questions workflow-building	3	396	11 يناير 2024

Workflow could not be activated

الموضوعات ذات الصلة