Workflows Saving but resetting to an older state

I am creating the workflow. Then I successfully test the workflow. It is working as it’s supposed to.
I save inbetween and everything seems fine.

Then I leave everything alone, close browser, etc. and come back later. The workflow is now in an older state than the latest one.

It feels a bit like a reset to some state before.

I cannot pinpoint certain timesframes unfortunately. Even looking at old executions I can see the actual workflow that SHOULD be the current one. Then I can copy it out of the execution and bring it back to the workflow editor and paste it there.

Had it already 2-3 times and basically lost a lot of effort in creating my workflows.

Maybe someone has an idea? Cache maybe?

N8N is self-hosted on Zeabur.
Version 1.90.1

P.s.: Might be the NEXT version? When I installed it, my API keys completely reset and it gives out an encryption key error.

Also the license key I had to add several times, because it was also acting like I have never added it.

I’d try use the production version. I think the latest pull for me today was 1.89.2.

That is a weird issue. I have seen it some time ago, but thought it was fixed.

The way API keys work has changed this might have reset your API keys (if you are talking about n8n API keys)

Could you maybe give us a bit more information on the setup?

1 Like

Switching to production did not solve it.

I am not sure what caused it in the end, but I could solve it by clearing the license and setting up a fix encryption key in my .env.

Now everything is persistent and stays as it should.

Thanks for the help guys

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.