> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/service-automation/configure-phase-behavior.md).

# Configure phase behavior

Configure phase completion, Result priority, Case routing and retries in Dublin 6.0.0.

**Phase behavior** controls when a phase completes, which business result it produces, and what happens after that result. Open it after **Definition** and **Service Flow** in the service wizard.

This Dublin 6.0.0 example uses one Execute Work Item and no Govern or Prove work. Adapt its settings to your own success criteria, then test successful, failed and retry paths.

### Read the settings in order

| Section               | Purpose in the interface                                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Completion**        | Decide when the phase's active work meets its completion requirement. The captured configuration shows **All active work completes**. |
| **Result**            | Define the business vocabulary and the rule used to select each result after completion.                                              |
| **Execution Rules**   | Configure execution rules. The captured example shows **No rules configured**.                                                        |
| **After Result**      | Choose the case action for each selected phase result.                                                                                |
| **Advanced Settings** | Configure retries for failed automation tasks.                                                                                        |

Completion and a negative business result are different. A Completion failure follows a phase/case failure path; it is not simply another business Result row. **After Result** actions apply only after Completion is satisfied and one Result row is selected.

The expanded **Completion** panel offers **All active work completes**, **At least N items complete**, **At least N items succeed**, and **Selected work completes**. A **Parallel Group counts as one Work Item** for this setting. The panel states that work which cannot finish because of timeouts, errors, or unmet minimums marks the phase and Case **Failed**. Choose the completion requirement before interpreting the Result rules; an unmet completion requirement does not select a negative Result row.

### Set Result priority deliberately

The example Execute configuration contains these Result rows:

| Priority | Result name            | Rule shown                          |
| -------- | ---------------------- | ----------------------------------- |
| 1        | Delivered              | All evaluated work succeeds         |
| 2        | At Least One Delivered | At least one item succeeds          |
| 3        | Partially Delivered    | Success and non-success are mixed   |
| 4        | At Least One Failed    | At least one item is not successful |
| 5        | Not Delivered          | No evaluated work succeeds          |

The interface evaluates rows **from top to bottom; the first match wins**. Drag rows to change their priority. Result names are editable business vocabulary, so do not infer behavior from a name alone.

*Figure 1. Priority is part of the configuration. Multiple conditions can match, but only the first matching Result is selected.*

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FFsS2eKqe3KiXcQj8l2qX%2Fphase-result-priority.png?alt=media&amp;token=75588039-de6c-43a5-a04c-fdce1bba24f0" alt="Execute Result rows with their rules and evaluation-priority guidance."><figcaption></figcaption></figure>

For example, a mixture of successful and unsuccessful work can satisfy both **At least one item succeeds** and **Success and non-success are mixed**. In the order shown, the earlier row wins. If your intended policy is to classify mixed work separately, review that priority before publishing.

### Map a Result to the case outcome

In this example there are **no Prove Work Items**, so the interface states that **Execute closes the case**. Each After Result selector offers:

| Case Status | Case Result     |
| ----------- | --------------- |
| Done        | Success         |
| Done        | Partial success |
| Done        | Failed          |
| Failed      | Failed          |

Figure 2. This example uses customized After Result mappings. Choose routing that matches your service’s business outcomes.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FvlqY9F0EXSADCKAvMvri%2Fphase-after-result.png?alt=media&amp;token=8aef856e-3f2d-4793-ab12-ed61f30213cc" alt="After Result selectors show the case Status and Result configured for each phase result."><figcaption></figcaption></figure>

For example, the screenshot maps Partially Delivered to Done / Success. To report a mixed outcome as partial success, select Done / Partial success and test a representative Case.

The deployment inherits phase settings from the service blueprint. Review the selected values before creating a package-specific override.

{% code collapsedlinecount="10" %}

```mermaid
flowchart TD
    A["Phase work reaches completion evaluation"] --> B{Completion outcome}
    B -->|Failure| C["Phase / Case failure path"]
    B -->|Satisfied| D["Evaluate Result rows in priority order"]
    D --> E["Select the first matching Result"]
    E --> F["Apply its After Result mapping"]
    F --> G["In this no-Prove example: close the Case"]
```

{% endcode %}

### Worked example: explain the selected rule in SC-3

In the recorded request-intake Case SC-3, Execute reports one of one Work Items finished and Work Item Done / Pass. Why this result/state? then shows how that recorded work result was evaluated.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FyXrJV1RAzQPk4to6RSVX%2F18-service-case-sc3-journey.jpg?alt=media" alt="SC-3 explains the completion, first matching result rule and end-success transition."><figcaption></figcaption></figure>

1\. Read CONFIGURED first: Execute completes when all its Work Items finish.

2\. Read OBSERVED: 1/1 Work Items finished.

3\. Read DECISION: all-positive at priority 1 matched Delivered. The any-positive rule also matched, but the earlier priority won.

4\. Follow the selected transition: end-success closed the Case and skipped downstream phases. Check Prove separately before reporting an independently verified outcome.

SC-3 also has Stop & Return input result=false with a configured response code of 200. HTTP 200 is not a technical error. How the intended negative business result should be passed into the Work Item/Case outcome is still being clarified; this run does not establish that mapping. Read the recorded phase rule and Prove check separately.

### Design the waiting path inside the Work Item

Pause for resume uses Before Wait and After Resume. All children in Before Wait finish before the token is generated. A valid continuation runs only After Resume; the normal workflow below or outside the pause does not continue.

Keep this action-level path separate from the phase Completion and After Result settings. Place required post-approval work inside After Resume, then test how the phase and Case finish with your selected rules.

For the resume request fields and a practical example, see [Work Items](https://docs.autommate.com/userguide/service-automation/create-work-items-and-pin-released-versions.md).

### Review retries and publish

Under Advanced Settings, review Retry failed automation tasks, Attempts, and Wait between attempts (sec). Before enabling retries, check whether repeating the affected work could duplicate an external change. Confirm how Attempts is counted for your execution path.

### Prepare a bounded retry test

1\. Use an isolated Work Item with local actions and an understood technical failure. First run it without retries and retain its Case, error and action record. Result No on Stop & Return is not an established technical-failure trigger for this exercise.

2\. In Advanced Settings, record Retry failed automation tasks, Attempts and Wait between attempts (sec). Use the smallest suitable retry setting supported by the form.

3\. Run the same test input and inspect the Work Item’s attempt records and timestamps. Count the initial attempt separately, then compare subsequent records with the configured value and delay.

4\. Check which actions ran again. If an earlier action could create a ticket, account or payment, do not use it for this local test.

5\. Keep the run unconfirmed if the attempt count or repeated scope is unclear. Confirm the product’s counting rule before presenting the configured number as total attempts.

Before Review & Publish, check Completion, Result order and every After Result mapping together. Include Prove when the service must verify its business result.

### Inherited settings and deployment overrides

**Default / Recommended transitions** means the deployment is using the inherited phase configuration without a local override. It can therefore inherit customized choices from the service blueprint. Changing phase behavior in the deployment creates a local customization and updates the indicator. Review the actual Completion, Result and After Result values alongside the label.

Review the configuration itself when explaining a Case result. A business Result name does not determine routing independently of its After Result setting.

A Prove Work Item must evaluate the intended success criterion. For example, after creating an account, check the target account rather than assigning a constant success value.

For a controlled demonstration, use a non-financial test outcome value. Treat configured service value separately from billed revenue and ARR.

### Pause timing

Pause for resume has no automatic expiry in Dublin 6.0.0 as of 13 October 2026. Do not design a timeout or escalation around an assumed token expiry. Treat the single-use resume token and any separate cancellation or escalation process independently.
