ARD 2.9 Flows are intermittently showing as Read Only even though not locked

Document ID : KB000115480
Last Modified Date : 20/09/2018
Show Technical Document Details
Question:
After upgrading to ARD 2.9 I noticed flows are intermittently opening as "READ-ONLY". I verified that the flow is not locked in TDM repository. When I have opened the flow from a main flow, I did not receive a message saying it was locked by another user. However, flow still appears as "READ-ONLY". This does not happen on every flow. It appears to be random, or at least, I have not been able to determine a pattern.
Answer:
The 'READ-ONLY' status has nothing to do with the flow being locked or not. It means the version you are looking at is not the latest version of the flow. This happens because the parent flow, that the subflow block is referencing, is an older version of the actual flow.

For example, I have a flow that have several different versions created along the way. If I open the latest version of the Flow saved in the TDM Repository (version 1.0.0.9).
Parent Flow

When I right-click on the subflow block, "Subflow_1", and select "Open Subflow in New Tab", the subflow opens as "READ-ONLY".
User-added image

Subflow_1

This happens because the parent flow is referencing an older version of the "Subflow_1" flow.  Since you cannot edit older versions of a flow, it opens in read-only.

To get around this you will need to open the most recent version of the subflow, by going to the "Manage" tab and click the "Revision History" button.
User-added image

The Revision History dialog window will open. Select the "Load Version" button to open the most recent version of the flow.
User-added image

Which will open the most recent version of the flow, and allow you to make your edits.