Symptoms
After upgrading to Event Processing 1.4.6, flows present in the Event Processing application might become read-only. When the issue occurs, the Event Processing UI can look as in the following example:
Note: This issue does not occur if using an Event Processing instance configured without persistent storage, nor when importing flows exported to JSON format from earlier versions of Event Processing.
Causes
Because of a change in the internal storage of flows, this issue can occur when flows were created using an earlier Event Processing version.
Resolving the problem
To make the flow editable again, complete one of the following steps:
- Duplicate the flow and use the duplicated flow (the original one can be deleted).
- Run the flow, then stop it. For more information, see Running a flow.
- Export the flow to the JSON format, then import it (the original flow can be deleted). For more information, see Exporting and importing flows.