# After All

### Overview

The **After All Component** is used at the end of a test flow to ensure that all connected components have completed execution before proceeding. It collects and processes all incoming messages before sending them to the output.

### Usage

This component is ideal for synchronizing multiple parallel branches in a workflow, ensuring all branches finish before continuing.

#### Input Ports

| Port | Description                                      |
| ---- | ------------------------------------------------ |
| `in` | Receives messages from all connected components. |

#### Output Ports

| Port  | Description                                                             |
| ----- | ----------------------------------------------------------------------- |
| `out` | Sends messages after all connected components have completed execution. |

#### Properties

| Property  | Type     | Description                                                                    |
| --------- | -------- | ------------------------------------------------------------------------------ |
| `timeout` | `number` | Maximum time (in seconds) to wait before timing out. Default is `180` seconds. |

#### Processing Logic

1. **Receives Messages**: Captures messages from all connected components.
2. **Tracks Completion**: Checks if all expected messages have arrived.
3. **Timeout Handling**: If not all messages arrive within the specified time, it times out and reports missing components.
4. **Sends Output**: Once all messages are received (or upon timeout), sends the collected messages to the output port.

### Notes

* **Ensures Completion**: Guarantees that all necessary components finish before execution proceeds.
* **Timeout Protection**: Prevents indefinite waiting by enforcing a timeout.
* **Parallel Synchronization**: Ideal for workflows with multiple parallel branches requiring synchronization.

This component is essential for orchestrating complex test flows where all processes must complete before continuing execution.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.appmixer.com/connector-configuration/utils/test/afterall.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.