Issue with Node Red

OpenRPA version: 1.4.54
OpenFlow version: v1.4.35
Using app.openiap.io or self hosted openflow: self hosted
Error message: After opening Node Red, I noticed that all my work was gone.
I don’t know what happened, but it’s like I opened a new Node Red, without any flow developed. Even a welcome message appeared.

Everything was working perfectly, but suddenly an error occurred.

Screenshot or video:
Attach a simple workflow from OpenRPA or NodeRED that reproduces the error/issue:

noderedlocal-error.log has the following content:
Mon, 14 Aug 2023 20:24:25 GMT express-session deprecated undefined resave option; provide resave option at …\Users\EA-BR22689\AppData\Roaming\npm\node_modules@openiap\nodered\dist\WebServer.js:164:30
Mon, 14 Aug 2023 20:24:25 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at …\Users\EA-BR22689\AppData\Roaming\npm\node_modules@openiap\nodered\dist\WebServer.js:164:30

noderedlocal-out.log has the following:
run
e[0me[1me[36mNodeJS version v18.16.0 Config C:\openflow\noderedlocal.enve[0m
e[0me[1me[36mStarting as service noderedlocale[0m
e[0me[1me[36mrun: C:\Users\EA-BR22689\AppData\Roaming\npm\node_modules@openiap\nodered\dist\index.jse[0m
17:24:21.63 Starting @openiap/nodered
otel_metric_url
otel_trace_url
ofid=noderedlocal
e[0me[1me[32m17:24:24.685 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mstarting openflow noderede[0m
e[0me[1me[32m17:24:24.728 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mVERSION: 1.4.35e[0m
e[0me[1me[32m17:24:24.728 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mConnecting to ws://dev-openflow.come[0m
Tracing initialized
e[0me[1me[32m17:24:24.863 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mConnected to ws://dev-openflow.come[0m
e[0me[1me[32m17:24:24.863 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36msignin with tokene[0m
e[0me[1me[32m17:24:24.984 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36msigned in as adminrpa with id 64498ebf0450e87168fec566e[0m
ofid=00a16c0325ad63421e0c8fd1b5d78364
e[0me[1me[32m17:24:24.984 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mQuery for user configiratione[0m
e[0me[1me[32m17:24:25.349 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mlistening on http://dev-openflow.com:1880/e[0m
e[0me[1me[32m17:24:25.349 e[0me[1me[37m[e[0me[2me[33mindex e[0me[1me[37m][e[0me[2me[33me[0me[1me[37m] e[0me[1me[36mEmit signed evente[0m
14 Aug 17:24:27 - [error] Node-RED runtime not started
14 Aug 17:24:32 - [warn] Using unencrypted credentials
e[0me[1me[32m17:27:16.373 e[0me[1me[37m[e[0me[2me[33mstorage e[0me[1me[37m][e[0me[2me[33msaveSettingse[0me[1me[37m] e[0me[1me[36m17:27:16e[0m
e[0me[1me[32m17:27:16.435 e[0me[1me[37m[e[0me[2me[33mstorage e[0me[1me[37m][e[0me[2me[33msaveSettingse[0me[1me[37m] e[0me[1me[36mRestart not needede[0m

There seem to be a small timing issue were nodered sometimes starts without getting workflow and credentials from the database. As long as hou did not making and actions inside nodered, simply restarting it will fix the issue.
If you did something in the empty nodered, then you need to find each nodered object in the noderee collection and restore and earlyer version and hope the history is complete enough to make amprober restore.

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