Consult the following checklist for possible causes:
Playing a flow is subject to the same limitations on features and capabilities that apply to generating a macro for the Host Access Transformation Services (HATS) runtime (see Limitations on features and capabilities when you play a flow).
When you load a flow the host editor prospectively checks the flow for the limitations on features and capabilities that apply when you are playing a flow (see Limitations on features and capabilities when you play a flow and Error or warning messages when you load a flow).
disabled:The
host editor disables the Play Flow icon
if the
working flow does not have an interface operation associated with
it.
When you play back a flow the host editor plays the contents of the working flow (see Using the working flow).
To add recent fixes or other modifications to the working flow save the modifications and reload the flow (see Saving changes to the working flow).
To play back a flow recording in the host editor -- especially a flow recording that you have just completed -- you must first incorporate the recorded material into the working flow.
You can play back an entire flow starting at the first node of the flow. You cannot begin a playback at some node other than the first node of the flow. You cannot play a disconnected path.
Either of two errors can cause the Flow Player Error window to open and display the error message Macro Error: Macro timed out:
Error message: "Macro Error: Recolimit reached, but goto screen not provided, macro terminating."
Typically this error indicates that the flow that you are playing back is caught in an endless loop (see Setting a screen recognition limit to prevent an endless loop during playback in the topic Playing a terminal flow).