Hi @Michel, it is indeed possible to change the timezone used by the Cron node. You can set any of the n8n environment variables for the desktop app as well, including the time zone ones:
To do so, you would need to edit the ~/.n8n/n8n-desktop.env file (MacOS) or the C:\Users\<username>\.n8n\n8n-desktop.env file (Windows, replace <username> with your actual username and add an entry like GENERIC_TIMEZONE=Europe/Berlin to the file.
Hi @Michel, once again many thanks for your feedback here!
Just wanted to quickly follow up on this as @ivov released a new version of the desktop app based on 0.160.0 today. This version should auto-detects the time zone and sets GENERIC_TIMEZONE (if missing) so you would no longer need to do this manually.
Your workflows should not be affected by the upgrade, you can simply run the installer for the new version and it should upgrade the desktop app while keeping your workflows.
That said, a backup is never a bad idea. The simplest way would be to download each workflow through the UI:
You could also use the CLI to export all workflows at once. This is described here:
The required executable from the desktop app would live in C:\Users\<username>\AppData\Local\Programs\n8n\resources\app\node_modules\n8n\bin (for Windows), so a one liner printing a JSON representation of all your workflows would be this one (you’d need to replace <username> with your Windows username):
Lastly, you could even automate it if you wanted to, using for example a workflow like this one: https://n8n.io/workflows/817 (this would require some adjustments, like using the desktop app’s URL http://localhost:5679/ for the REST API requests instead of the default one).