Restart node-red nodes jump between tabs, lines missing

When I restart node-red. I have nodes (specifically the worldmap dashboard node) all jumping to the first tab. and disconnect from the nodes they were connected to.

When I export and import the flow I do not have this issue.

Also I am missing a few connecting lines upon restart.

What could be the cause of this?

what version of NR and node.js? (you can get this from the startup log - copy and paste the startup to a reply)
What platform are you runing on?
After you import the flow and fix and deploy it, does the restart cause the issue again?
How big is the flow?
Have you tried it on another device?

Microsoft Windows [Version 10.0.19043.1348]
(c) Microsoft Corporation. Alle rechten voorbehouden.

H:>node-red
29 Dec 13:58:16 - [info]

Welcome to Node-RED

29 Dec 13:58:16 - [info] Node-RED version: v2.1.4
29 Dec 13:58:16 - [info] Node.js version: v16.13.1
29 Dec 13:58:16 - [info] Windows_NT 10.0.19043 x64 LE
29 Dec 13:58:18 - [info] Loading palette nodes
29 Dec 13:58:21 - [info] Worldmap version 2.23.5
29 Dec 13:58:21 - [info] Dashboard version 2.30.0 started at /ui
29 Dec 13:58:22 - [warn] ------------------------------------------------------
29 Dec 13:58:22 - [warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red
29 Dec 13:58:22 - [warn] ------------------------------------------------------
29 Dec 13:58:22 - [info] Settings file : C:\Users\xx.node-red\settings.js
29 Dec 13:58:22 - [info] HTTP Static : C:\Users\xx.node-red\static
29 Dec 13:58:22 - [info] Context store : 'default' [module=memory]
29 Dec 13:58:22 - [info] User directory : C:\Users\xx.node-red
29 Dec 13:58:22 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Dec 13:58:22 - [warn] Flows file name not set. Generating name using hostname.
29 Dec 13:58:22 - [info] Flows file : C:\Users\xx.node-red\flows_xxx8.json
(node:29984) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\Users\xx.node-red\node_modules\node-red-dashboard\package.json' of 'none'. Please either fix that or report it to the module author
(Use node --trace-deprecation ... to show where the warning was created)
29 Dec 13:58:22 - [warn]

And the answers to the rest are???

What platform are you runing on?
Windows

After you import the flow and fix and deploy it, does the restart cause the issue again?
Yes

How big is the flow?
Maybe 100 nodes

Have you tried it on another device?
Not yet

@PiMo131 can you check the browser's JavaScript console for any errors when you load the editor and import the flows?

Could you also post a screenshot of the problem (and a matching good screenshot too)

Can you provide the flow to see if someone can reproduce it?

Sorry for the late reply I was on holiday. The flow is bigger than the message body limit. So I added the flows as an attachment
Backup.json (76.2 KB)

I also added pictures of the problem and the fixed problem: