# Messages and updates

> ![subprocess with multiple non‑interrupting boundary messages, each handled independently.](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-subprocess-with-multiple-non-interrupting-boundary-messages-each-handled-independently-620751-b436592a.webp)

## Handle updates without interrupting work (non‑interrupting boundary messages)

![subprocess with multiple non‑interrupting boundary messages, each handled independently.](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-subprocess-with-multiple-non-interrupting-boundary-messages-each-handled-independently-620751-b436592a.webp)

**Use when**

* You need to process updates while a task is in progress.
* Updates should not halt the main work.

**Pattern in simple words**

1. Start.
2. Subprocess: Deliverable preparation.
3. Non‑interrupting boundary message Updated requirements received: User task Log new requirements. Service task Adjust project plan. End Requirements handled.
4. Non‑interrupting boundary message Compliance rule change received: User task Review rule change. Service task Update compliance checklist. End Compliance handled.
5. Main path: Deliverable preparation completes. End Deliverable completed.

   :::note
   Each message triggers a small side flow without stopping the main work.
   :::

   **Other scenarios**

* Finance: Credit‑risk review receiving new market data.
* Healthcare: Care‑plan preparation receiving updated lab results.
* Manufacturing: Product design updates from regulation changes.
* Retail: Campaign plan updates with product revisions.
* Telecom: Network upgrade planning updates with compliance changes.

## Cancel during a task (interrupting message)

  ![A subprocess that can be cancelled by an interrupting message.](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-a-subprocess-that-can-be-cancelled-by-an-interrupting-message-620755-862f50f4.webp)

**Use when**

* Work must stop immediately on a cancel request.
* A clear message should abort the task.

**Pattern in simple words**

1. Start.
2. Subprocess: Process booking.
3. Interrupting boundary message Cancel request: User task Stop and notify. End Cancelled.
4. Normal path: Process booking completes. End Completed.

   :::note
   The interrupting message cancels the active work at the subprocess boundary.
   :::

   **Other scenarios**

* Finance: Loan withdrawal cancels underwriting.
* Healthcare: Patient cancels a scheduled procedure.
* Manufacturing: Cancel production order before run.
* Retail: Cancel order before shipment.
* Telecom: Cancel new service setup.

## Event‑driven dispatcher (message start)

  ![A process that begins with a message start and creates a ticket.](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-a-process-that-begins-with-a-message-start-and-creates-a-ticket-620759-b7d2893e.webp)

**Use when**

* A new external message should start a process.
* Each event spawns an independent workflow instance.

**Pattern in simple words**

1. Message start: New email received.
2. Service task: Create support ticket.
3. Send task: Confirm receipt.
4. End Ticket created.

   :::note
   Each incoming message creates a new instance.
   :::

   **Other scenarios**

* Finance: Vendor request message starts onboarding.
* Healthcare: Referral message starts patient intake.
* Manufacturing: Defect report starts QA process.
* Retail: Online order starts fulfillment.
* Public sector: Citizen inquiry opens a case record.