Suspend and resume workflow runs

Know how to suspend and resume a workflow run automatically.

Action

Wait for Callback - This action allows you to pause a workflow execution until an inbound event occurs, at which point the execution is automatically resumed. The event can be triggered by sending an HTTP request that includes the workflow’s execution_id and the provided URL.

Wait time - Wait time defines the number of days the system waits for the inbound events to occur, with a maximum limit of 25 days. The inbound event must occur within the specified wait time, else the workflow remains in a suspended state and cannot be resumed. If the event occurs after the specified wait time, the workflow resume request is rejected, and the workflow execution status is marked as failed.

You can customize the wait time by clicking the Execution settings link or from the Workflow settings page.

Access

You can set the access of the webhook URL to public or private based on your requirements.

Public - Under public access, the webhook URL can be accessed over a public network.

Private - Under private access, the webhook URL cannot be accessed over a public network.

The following two types of URLs are supported under the private access.

  • Internal URL - The internal webhook URL is accessible only from within your IBM® webMethods Integration network or by IBM webMethods Integration applications across tenants.

  • Private URL - The private webhook URL is accessible only from within your privately configured network. This URL cannot be accessed from within your IBM webMethods Integration network or by IBM webMethods Integration applications across tenants.

Stop workflow - You can manually stop the workflow execution while it is in the suspended state. This prevents the workflow from staying suspended if the callback event does not occur. To do this, click the console panel icon on the canvas, and then click Stop workflow.

Note:
  • The URL used to trigger the inbound event is secured with tenant credentials. Therefore, you must include your tenant credentials when sending the HTTP request with the URL.
  • The duration for which the workflow remains suspended is not included in the calculation of the total transaction count for the workflow execution.
  • While designing the workflow, you cannot add the Wait for callback action before the Return Data on sync webhook action or inside the Global error handler or Loop action. Attempting to do so results in an error.