Beginning in IBM Platform Process Manager 8.2, the process to rerun an exited flow in Flow Manager is different. In IBM Platform Process Manager 8.1 and earlier releases, when a flow contains a job that fails, you can rerun it by using the steps below.

For example, here is a flow that contains errors:

If you investigate the exited job and decide that you do not want to rerun it, you can right-click the exited job and mark it as Complete. Then, you can rerun the remaining jobs in the flow.

If you follow these steps in IBM Platform Process Manager 8.2 and later releases, you receive the following error:

No starting points or exited items. Flow cannot rerun.

Also, you cannot select Job_2 as a start point, because the Set as starting point to rerun flow option is not available when you right-click the job:

You could run each job individually using the Run option shown above. However, if you have many subsequent jobs, you would have to run the jobs sequentially, because you can run only one job at a time. 

Rerun Flows in IBM Platform Process Manager 8.2

Here is the process to use in IBM Platform Process Manager 8.2 to rerun flows with no further manual intervention:

1. Right-click Job_2 and select Complete:
   
2. Right-click Job_2 and select Set as starting point to rerun flow:
   
3. Right-click the Flow Instance and select Rerun:
   
4. Select the appropriate radio button for your situation and click OK:
   
   At first, the starting point job shows as waiting:
   
   Then, it starts running along with the remainder of your flow, assuming that there are no further errors:
   

See SAS Note 65855, "A flow rerun cannot start from a pending job in IBM Platform Process Manager 10.1," for a patch for that version.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	Platform Process Manager	Microsoft® Windows® for x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8 Enterprise x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8 Pro x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8.1 Enterprise 32-bit	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8.1 Enterprise x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8.1 Pro 32-bit	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 8.1 Pro x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows 10	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows Server 2008 R2	8.2		9.4 TS1M0
		Microsoft Windows Server 2008 for x64	8.2		9.4 TS1M0
		Microsoft Windows Server 2012 Datacenter	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows Server 2012 R2 Datacenter	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows Server 2012 R2 Std	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Microsoft Windows Server 2012 Std	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Windows 7 Enterprise x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Windows 7 Professional x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		64-bit Enabled AIX	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		64-bit Enabled Solaris	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		HP-UX IPF	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Linux for x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7
		Solaris for x64	8.2	10.29	9.4 TS1M0	9.4 TS1M7

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

After you mark an exited job as complete, there is no intuitive way to rerun the exited flow from the next waiting job. This SAS Note outlines the steps to follow to rerun the exited flow.

Type:	Usage Note
Priority:

Date Modified:	2017-05-17 11:14:41
Date Created:	2017-05-05 06:42:51