--- title: State changes for event tasks in groups description: The original and duplicate event tasks in the Similar tasks group move through different states until the original task is closed. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/transition-states-of-event-task.html release: australia topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Creating similar tasks groups, Structured workflows for Exercises, Manage, Business Continuity Management, Governance, Risk, and Compliance] --- # State changes for event tasks in groups The original and duplicate event tasks in the Similar tasks group move through different states until the original task is closed. The state transitions of the original and duplicate event tasks are explained in the table.
Description Task state
An event contains similar tasks grouped together. The event from the list where similar event tasks are grouped together is shown in the example. \[Omitted image "event-started-for-sim-task-grp.png"\] Alt text: Similar tasks group.
State the **Original task** field before starting the event. Before starting the event, the **Original task** field in the Similar tasks group is empty and in the read-only state. \[Omitted image "event-task-ori-task-empty.png"\] Alt text: Original task empty.
After an event is started, the original task is auto-assigned. The first task of the event, such as t4 \(EVNTSK0010020\) of group 2 in the example, becomes the original task of the Similar tasks group. The example shows that task 4 \(t4\) does not have any dependency. \[Omitted image "event-ori-task-open.png"\] Alt text: Original task Open.\[Omitted image "event-starts-ori-task-updated.png"\] Alt text: Original task updated.
States of original and duplicate tasks The original task is updated to the **On hold** state and the duplicate task is in the **Pending** state. \[Omitted image "event-sim-task-grp-refreshed.png"\] Alt text: On hold state.For context, the worknote for the original task is updated such that the task has been moved to **On hold** because it was grouped by the similar task groups. \[Omitted image "event-ori-task-worknote-updated.png"\] Alt text: Worknote.
The dependencies in the similar tasks group are closed. Task 4 is dependent on task 3, task 3 is dependent on task 2, and task 2 is dependent on task 1. Therefore, it is closed first. \[Omitted image "event-ori-task-open.png"\] Alt text: Original task Open.
After closing t1, t2 moves to the **Open** state. The task, t2, is open.
After closing t2, t3 moves to the **On hold** state. The task, t3, is on hold.
Since all tasks in the group are On hold, the original task \(t4\) moves to the **Open** state. The task, t4, is open.
Final step. After closing the original task, the duplicate task moves to the **Closed duplicate** state automatically. The duplicate task \(t3\) moves to the **Closed duplicate** state automatically. \[Omitted image "event-closed-dup-task.png"\] Alt text: Closed duplicate.
You can unlink an event task from the similar tasks group by selecting the **Unlink similar tasks group** UI action in the event task. You can re-trigger an original task as a manual task and complete its workflow like a regular event task by selecting the **Re-trigger as a manual task** UI action in the event task. It moves the original task to the **Open** state, but its duplicate task stays in the **Closed duplicate** state. **Parent Topic:**[Creating similar tasks groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/identifying-running-dup-tasks-once.md)