> For the complete documentation index, see [llms.txt](https://docs.ecotone.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecotone.tech/modelling/asynchronous-handling.md).

# Asynchronous Handling and Scheduling

{% hint style="info" %}
Works with: **Laravel**, **Symfony**, and **Standalone PHP**
{% endhint %}

## The Problem

You added async processing, but now you can't tell which messages are stuck, which failed silently, and which will retry forever. Going async required touching every handler — adding queue configuration, serialization logic, and retry strategies individually.

## How Ecotone Solves It

Ecotone makes any handler async with a single `#[Asynchronous]` attribute. Retries, error handling, and dead letter are configured at the channel level And switch between synchronous and asynchronous execution without changing your business code.

***

{% content-ref url="/pages/Sg5toYJ9X9EeB3jWTxnd" %}
[Asynchronous Message Handlers](/modelling/asynchronous-handling/asynchronous-message-handlers.md)
{% endcontent-ref %}

{% content-ref url="/pages/647sf4AWgVVwE2UWLLII" %}
[Asynchronous Message Bus (Gateways)](/modelling/asynchronous-handling/asynchronous-message-bus-gateways.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M2wmTRZNDPSMp7IBCsL" %}
[Scheduling](/modelling/asynchronous-handling/scheduling.md)
{% endcontent-ref %}

{% content-ref url="/pages/W1Ddrljy41zrP0GKodAt" %}
[Dynamic Message Channels](/modelling/asynchronous-handling/dynamic-message-channels.md)
{% endcontent-ref %}

## Materials

### Demo implementation

You may find demo implementation [here](https://github.com/ecotoneframework/quickstart-examples/tree/main/OutboxPattern).

### Links

* [Queues and Streaming Channels Architecture](https://blog.ecotone.tech/async-failure-recovery-queue-vs-streaming-channel-strategies/) \[Article]
* [Asynchronous processing with zero configuration](https://blog.ecotone.tech/message-channels-zero-configuration-async-processing/) \[Article]
* [Asynchronous PHP To Support Stability Of Your Application](https://blog.ecotone.tech/asynchronous-php/) \[Article]
* [Asynchronous Messaging in Laravel](https://blog.ecotone.tech/ddd-and-messaging-with-laravel-and-ecotone/) \[Article]
* [Testing Asynchronous Messaging](/modelling/testing-support/testing-asynchronous-messaging.md) \[Documentation]
* [Testing Asynchronous Message Driven Architecture](https://blog.ecotone.tech/testing-messaging-architecture-in-php/) \[Article]


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ecotone.tech/modelling/asynchronous-handling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.