Add Native Pause/Delay Capability to Cloud Pak for AIOps Runbook Actions

In IBM Cloud Pak for AIOps, runbook actions (manual, semi‑automated) currently execute sequentially without the ability to introduce a controlled wait or pause interval directly within the runbook flow.

For many remediation and operational scenarios, it is necessary to allow a system or service time to stabilize after an action is performed (for example, after a restart, configuration change, or operator intervention) before initiating any subsequent actions.

Today, implementing such delays requires embedding workaround logic (for example, custom scripts or automation‑level pauses), which increases complexity and reduces the clarity and maintainability of runbooks.

Enhancement Request

Provide a native pause/timer capability within Cloud Pak for AIOps runbooks that can be configured before or after a runbook action, including manual and semi‑automated actions.

The pause capability should allow runbook authors to define a configurable delay (for example, seconds or minutes) during which the runbook execution is intentionally paused before proceeding to the next action.

Business and Technical Value

• Enables controlled stabilization periods between runbook actions

• Improves reliability of remediation workflows by preventing premature follow‑up actions

• Reduces the need for custom scripting or automation workarounds

• Simplifies runbook design and improves readability and maintainability

• Aligns runbook behavior more closely with real‑world operational requirements