---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Import automated tasks and start an event

# Import automated tasks and start an event {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Import the automated task from the business continuity plan in an actual event. Utilizing automated tasks during an actual event enhances efficiency and reduces response time for users.

## Before you begin

Role required: sn_bcm.planner, sn_bcm.program_manager

## Procedure

1. Navigate to WorkspacesBusiness Continuity Workspace.
2. In the List view, navigate to crisis eventsPending and select New.  
   The Create New Event form is displayed.
3. In the Details tab of the Create New Event form, fill in the required fields.  
   Note:  
   For a crisis event, the event type is Actual.
   For more information on the fields, see [Create Crisis Event form](https://servicenow-prod.fluidtopics.net/Sa4JgNgRmN9feIorrf3qIg "Use the Create Crisis Event form in BCM UIB Workspace to add details about a crisis event.").
4. Navigate to the Planning list in the Workspace view and select the plan associated with the event.  
   When you select the plan, the associated tasks are pulled into the event. The tasks are displayed on the Event tasks tab. When the tasks displayed on the Event tasks tab
   have a dependency between them, they are executed in a sequential order.
5. Select Start event.  
   Upon initiating an event, the event tasks that do not have any dependency between them are executed. When a task is completed, the subsequent tasks that depend on it are executed. For example, when a task transitions
   to the Closed incomplete or Closed failed state, you have the option to select the task and review its activity details. If an error message is displayed on the screen,
   you can examine it to identify the issue and take appropriate corrective measures. For instance, if the error message indicates that the code variable must be a positive value, you can update the code variable
   accordingly.

   If the task transitions to the Closed failed state, then its dependent tasks are not triggered. In the event that a task is in the Closed incomplete or Closed failed state, an email notification is sent to the backup assignee, informing them that the automated flow has encountered an error and manual intervention is necessary from the backup assignee.
6. Select Re-trigger automation.  
   The automated flow is triggered for execution once more.
7. If the automated flow fails again, select Re-trigger as a manual task.  
   The task transitions to the Open state.
   1. Update the event task and select Work in progress.
   2. Select Closed complete.  
      You have the option to manually update the event task. Once you mark the task as Closed complete, the subsequent event task is automatically triggered. If the next task is a manual task, its assigned user can proceed to complete the workflow for the event task.
   {#import-the-automated-task-in-an-event__substeps_zbq_xx1_3bc}
8. Select Save.  
   The event task is then saved within the instance.

*[\>]: and then