In the SAS Management Console Schedule Manager plug–in, flow contents might be lost when more than one person uses Edit Flow in the same flow. That is, the flow is empty. Also, when you make changes to a flow, the flow might be empty the next time you view it. This problem can occur when two people edit the same flow concurrently and both save the flow, even if no changes have been made.

There is no indication of a problem until you check the flow contents. Once you find that the flow is empty, your only options are to rebuild the flow or recover it from a backup.

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix for this issue enables you to turn on a different behavior. With that behavior, you are notified of the problem and can save the flow in its current state. However, changes made in other sessions might still be lost.

After installing the hot fix, you must edit your sasmc.ini file to enable a new behavior. Add the option to
-Dsas.sch.RecoverOnMetadataWriteFailure=true to JavaArgs_1=-Xmx1024m, as shown below:

With this option enabled, when you edit a flow and attempt to close it, you might see the following dialog box. You see this dialog box if the hot fix has been applied and the sasmc.ini change was made.

This message indicates that you are about to lose your flow contents because someone else has also made changes.

Note: Failure to follow the instructions below will almost certainly cause the flow to be left in an empty state.

1. Click OK. In some cases, a second dialog box is displayed.

.

2. Click OK. You will be left in the Flow Editor, showing the original Flow.
3. Right-click and select Save Flow.
4. Right-click and select Close Flow.

Important: Under no circumstances should you select Refresh on either the Flow or Schedule Manager.

If you happen to notice a flow that is empty, it is possible that someone still has a copy available in their SAS Management Console session. If they do, then edit that flow, move a node on the flow (for example, a job or subflow), and click Save. Then select Refresh in the SAS Management Console session that showed the empty flow.

A similar issue can occur with new flows. The same recovery procedures apply.

Operating System and Release Information

A fix for this issue for SAS Management Console 9.3_M2 is available at:

A fix for this issue for SAS Management Console 9.3_M1 is available at: