cjworkbench Workflow becomes read only after several hours

Encountered three times (different workflows): create a workflow and try to edit it after several hours. It works as read only, can't edit or create a new tab (tab shows but can't move to it or rename it and disappears when browser is refreshed). Last workflow tested was last edited 15 hours back. Using Chrome on Win 10.
I can still start a new workflow. Further, I found if I go back to Workflow List (my workflows) and open the read only one, it becomes editable [failed to reproduce later, may be server or connectivity or load issues].

Oct 09 '19 03:10 abedkhooli

Thank you for reporting this issue. It's new to us.

Could you please try to reproduce this while Chrome Developer Tools is open? I'd be interested to see what's written in the "Console".

Also: what version of Chrome?

To clarify: after browser refresh, everything goes back to normal?

Oct 09 '19 13:10 adamhooper

I am keeping a workflow open to test. Using Chrome 77 (latest). Refresh had no effect. Signed in with Google account (still logged in). Error (repeated several times, some ws are to intercom: wss://nexus-websocket-a.intercom.io/): WorkflowWebsocket.js:27 WebSocket connection to 'wss://app.workbenchdata.com/workflows/35188' failed: Unknown reason n @ WorkflowWebsocket.js:27 WorkflowWebsocket.js:88 Websocket closed. Reconnecting in 1000ms Warning: Manifest: property 'start_url' ignored, should be same origin as document. storage.googleapis.com/production-static.workbenchdata.com/images/app-icons/manifest.json:1 Also:warning and intercom ws errors show at https://app.workbenchdata.com/workflows/

Temp fix: close all WB browser tabs then open a new tab (warning still shows in console but WF works).

Oct 09 '19 13:10 abedkhooli