Synchronizing parent and child incidents

concept australia Updated Sep 10, 2026 1 min read parent-child-state-sync.md
Raw file servicenow.com

The state of a child incident follows the state of its parent incident for most incident states, which keeps related incidents aligned without manual updates.

Parent state

On hold reason (parent)

Child state

On hold reason (child)

In Progress

N/A

In Progress

N/A

On Hold

Awaiting Change, Awaiting Problem, or Awaiting Vendor

Same as parent

Same as parent

On Hold

Awaiting Caller

Not updated

Not updated

Resolved

N/A

Resolved.The Activity log in the child incident form is updated with the resolution notes copied from the parent incident.

N/A

Closed

N/A

Not closed.Child incidents must be closed by the caller or by the system based on the auto-closure property.

N/A

Canceled

N/A

N/A

N/A

**Note:**

This table applies only to standard incident life cycle states. When a parent incident is proposed or accepted as a major incident, the states of any associated child incidents do not change automatically. For more information, see Managing major incidents.

When an incident has a child incident, the following actions take place:

  • If an ITIL user reopens the parent incident, both the parent and child incidents reopen. Both the parent and the child incident state is set to In Progress.
  • If an employee self-service (ESS) user reopens the parent incident, the parent incident state is set to In Progress but the child incident is not reopened.
Search documentation
Search document titles and file paths on the australia branch