Hi @MutedJam
Thank you very much for your help. Hopefully, Jon enjoys his well-deserved break.
OK, so we are not receiving an error with the export command at the moment and have spent quite some time trying to reproduce different install flows so as to determine where the original error occurred from, so as to help out the community, which we will report back on this once we have something worth reporting.
Despite trying many many angles, we are still unable to import back in, so what would really help would be if you could provide the code that you use in the Execute Command node for importing back.
We have searched the machine and are not finding a workflow.json file anywhere to reference to so if you happened to know the flow that n8n uses to export and import on the windows desktop version, that would be very helpful too, for all windows users as well. Something like the following would be great:
To export in windows desktop, use the Execute Command node with: C:\Users\User\AppData\Local\Programs\n8n\resources\app\node_modules\n8n\bin\n8n.cmd export:workflow --all
This saves the backup file to: ???
To import that backup file, use the Execute Command node with: ???
Just those few pieces of information will help all future windows users so thank you very much if you are able to help with that.