I run n8n with Docker with the image tag “latest-debian”. Every night, containers are automatically updated if new image is available, and since the version 0.119.0, I have one workflow with the status “Unknown” (but working perfectly):
The strange thing is that the workflow with this status is a copy of another workflow which have the status in success.
The purpose of the workflow is just to check my RSS feed, and sends me a Telegram notification if there is a new article. The only difference with other workflows is the source of RSS feed.
I’ve tried to use the image “0.118.0” or “0.118.1” ro rollback and check; but the problem comes back
It’s not a “big” problem as the workflow is working, but if possible to check this…
So just to confirm. That did not happen before with version 0.118.0/1 and it only started once you did upgrade to 0.119.0? And now even if you downgrade the problem does not disappear?
Hi @jan, I’ve started to use n8n since 0.118.0 and this problem was not present (every status was in “Success”). It’s really since the upgrade to image tag 0.119.0.
And yes, if I “downgrade” to tag image 0.118.0/1, status still in “Unknown”, even if I uncheck/check “Active”.
Not sure I understand. So if you downgrade, it still produces new executions with the status “unknown” or do you mean that the old executions do still get displayed as “unknown”.
Hello,
we are using n8n 1.30.0 in production and the infrastructure is to call processing by WebHooks, it’s deployed on K8 cluster and there we have a few pods with 300m CPU and 300Mi-1000Mi Memory.
Everything works nice but when we got a lot of requests our Workflows stacks in Unknown status and no errors are shown not event the steps where they are stopped.
