You can resume playing a workflow instance that has been paused. This is done by pressing Play within the workflow’s trigger’s mini toolbar. What happens next depends on the type of the most-recently executing activity:
•Batch audience: the workflow enters a Playing state, as does the batch audience.
•Interactive activity: the workflow enters a Playing state, as does the interactive activity. Any immediately-downstream activities also commence Playing.
•Delay: if the original delay duration has not passed, the workflow enters a Playing state, and the delay’s state is set to Counting Down Delay. If the duration has passed, the workflow enters a state appropriate to the current or most recent activity (e.g. if an audience is Playing, the workflow is also Playing; if all offers are Completed, the workflow is also Completed). The delay itself enters a Completed state.
•Wait for Event: if its trigger is manual, the workflow enters a Playing state, as does the wait for event. If the wait for event’s trigger is scheduled, and the scheduled time has not passed, the workflow enters a Playing state and the wait for event a Waiting for Trigger state. If the scheduled time has passed, the workflow enters a state appropriate to the current activity, and the trigger is fired.
•Export: the workflow enters a state appropriate to the current activity, and the export enters a Completed state (execution thereof having finished prior to the workflow entering a Paused state).
•Offer activity: the workflow enters a state appropriate to the current activity, and the offer activity enters Completed state (execution thereof will have finished prior to the workflow entering a Paused state).
•Decision offer activity: as per offer activity.
•Control: the workflow enters a state appropriate to the current activity, and the control enters a Completed state.