Remedial actions using Playbook

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Remedial actions using Playbook

    Remedial actions using Playbook in ServiceNow’s Investigation Framework enable you to resolve Configuration Item (CI)-related issues directly within the Investigate tab of the Incident record page. These actions, such as ending a process or restarting a service, provide interactive, guided remediation steps through a playbook interface accessible from the contextual side panel. This capability helps streamline incident resolution by controlling and tracking each step of the remediation process.

    Show full answer Show less

    Key Features

    • Playbook Integration: Playbooks guide the execution of remedial actions step-by-step, allowing you to monitor current and historical remediation processes on affected or caller CIs.
    • Remedial Actions Available:
      • End process: Stop processes on CIs, with specific workflows for Device and Server classes (including user approval or change request creation).
      • Restart service: Restart services on CIs, also requiring user approval or change requests depending on the CI class.
    • Contextual Side Panel: Access and execute playbooks, view current and historical remediation actions, and manage ongoing remediation through controls such as canceling actions.
    • CI Scope: Remedial actions can be performed on both affected CIs and caller CIs associated with the incident, supporting device endpoints (DEX) and Service Operations Workspace (SOW) views.
    • Concurrency Controls: By default, concurrent or duplicate remedial actions on the same CI are prevented, but you can configure the system to allow concurrent executions if needed.

    Practical Use and Configuration

    • The Investigation Framework and Remedial Action Framework applications must be installed and configured to enable this feature.
    • Remedial actions appear on the Investigate tab only if configured to display, and the playbook interface is available on the Incident record’s side panel.
    • For servers, executing remedial actions requires creating and providing information for a standard change request, ensuring compliance and governance.
    • User approval is required before executing remedial actions on device endpoints, adding an additional control layer.
    • You can view and manage remedial action statuses such as New, In Progress, Completed, Canceled, or Failed within the playbook panel tabs.

    Key Outcomes

    • Accelerate CI issue resolution by performing guided remedial actions directly from the incident interface.
    • Maintain control and visibility over remediation steps and their statuses through the playbook’s current and history views.
    • Ensure compliance with change management processes by integrating change requests for server-related remedial actions.
    • Improve incident handling efficiency by allowing remediation on both impacted and related caller CIs.
    • Customize remediation concurrency settings to fit your operational needs and reduce potential conflicts.

    Resolve the CI-related issues using the remedial actions using Playbook in the Investigate tab.

    The Investigate tab includes the following types of remedial action to resolve CI-related issues:
    • End process
    • Restart service
    These remedial actions are available on the Investigate tab only if the following conditions are met:
    Remedial actions use playbooks to resolve CI issues. Playbook provides you with an interactive UI to guide and execute the remedial actions step by step. With a playbook, you can control every execution step of the remediation process. Playbook is available on the contextual side panel of the Incident record page. When any remedial action is performed, that remediation process is added to a playbook. You can then select the playbook (Playbook icon) icon on the contextual side panel to open the playbook on a separate panel and execute the process. The playbook panel displays the following tabs:
    • Current: Displays the current list of playbooks that trigger the remedial action, including both processes and services run on the affected CIs or caller CIs with status New and In Progress.
    • History: Displays the historical list of playbooks, remedial actions including both processes and services run on the affected CIs or caller CIs with status Completed, Canceled, or Failed.
    You can perform remedial actions on both the affected CIs and the caller CIs associated with the incident record. The caller CIs are the CIs that are assigned to the caller.
    Note:
    If the CI is DEX supported, the remedial actions playbook for the DEX actions are displayed. If the CI is SOW or default view supported, the remedial actions playbook for SOW actions are displayed.
    You can cancel an ongoing End process or Restart service remedial action playbook. To cancel a remedial action playbook, select the remedial action playbook and select the menu (Menu icon) icon and then select Cancel action option. After the remedial action playbook is canceled, the corresponding action is also canceled. Then, the status of the remedial action is displayed as Canceled in the History tab of the playbook panel. To view the reason for cancellation, select the View reason option on the playbook. This option isn’t available if any of the following are true:
    • The remedial action is already in Canceled status.
    • The corresponding CI action record of the remedial action is already in progress.
    • The change request has already moved to implement state for actions associated to CIs of type server.

    The Remedial actions section on the Investigate tab also contains the Current and History tab to display the list of remedial actions performed. By default, this section displays the list of remedial actions for the primary CI or current CI. You can switch the Show actions performed on all CIs in this incident toggle to display the list of remedial actions for all the CIs associated with the Incident.

    Playbook is available only if both the Remedial Action Framework [com.snc.sn_reacf] application and the Investigation Framework [sn_invest_fwk] application are installed and configured, as well as if the remedial actions are triggered.

    Note:
    You can't execute concurrent or duplicate remedial actions when a remedial action is in progress on a process or service for a CI type device or server. You also can't execute concurrent or duplicate remedial actions on the same CI until the previous remedial action execution is completed. You can change this behavior and allow concurrent execution of the remedial action by selecting the Allow concurrent execution option for Remedial Action Type. For more information, see Configure the Remedial Actions Framework.

    End process

    The End process remedial action is available with the following metric information cards:
    • Top processes By Memory
    • Top processes By CPU
    Select the CI and then select End process to stop the process running on the CI. The remediation process then is added to the playbook. Select the Playbook (Playbook icon) icon from the contextual side panel to open the playbook on a separate panel and execute the process. You can execute the End process remedial action for the following CI classes:
    • Device: For this CI class, a two-step process is executed where you must get the user approval before the End process remediation process can be executed. After it’s approved, you can directly stop the process on the device, which is also known as the endpoint.
    • Server: For this CI class, you must create a change request before the End process remedial action can be executed using a standard change request. You must also provide additional information to create a change request.

    Restart service

    The Restart service remedial action is available with the Services metric information card.

    Select the CI and then select Restart service to restart the services running on the CI. The remediation process then is added to the playbook. Select the Playbook (Playbook icon) icon on the contextual side panel to open the playbook on a separate panel and execute the process. You can execute the Restart service remedial action for the following CI classes:
    • Device: For this CI class, a two-step process is executed where you must get the user approval before the Restart service remediation process is executed. After it's approved, you can directly restart the services on the device, which is also known as the endpoint.
    • Server: For this CI class, you must create a change request before you can execute the remedial action using a standard change request. You must also provide additional information to create a change request.