> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/broker/cybusmq/configuration/synchronous-subscribe-handling.md).

# Synchronous SUBSCRIBE Handling

CybusMQ synchronous SUBSCRIBE handling ensures the cluster is ready before sending SUBACK, preventing message loss during overload scenarios.

CybusMQ processes SUBSCRIBE requests synchronously across the cluster. The broker only sends the SUBACK response when all nodes are ready to route messages to the subscribing client.

## How It Works

When a client sends a SUBSCRIBE request, CybusMQ performs the following steps before sending SUBACK:

1. Replicates the subscription data to all cluster nodes.
2. Updates routing tables on all nodes.

This synchronous approach ensures that when a client receives SUBACK, the cluster is ready to deliver messages immediately.

## Message Loss Prevention

During overload scenarios, asynchronous subscription processing can cause the first few messages to be lost after SUBACK is sent. CybusMQ's synchronous approach prevents this by ensuring all cluster nodes are ready before confirming the subscription.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/broker/cybusmq/configuration/synchronous-subscribe-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.