Skip to content

fix(mnq): add question to faq #5569

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

fix(mnq): add question to faq #5569

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion pages/queues/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,4 +21,10 @@ We currently implement the API endpoints listed [here](/queues/reference-content

## How is Scaleway Queues billed?

Billing is based on [queue volume](/queues/concepts/#queue-volume) - the combined size of the messages travelling through queues. For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/).
Billing is based on [queue volume](/queues/concepts/#queue-volume) - the combined size of the messages travelling through queues. For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/).

## Do Scaleway FIFO queues support the `MessageGroupId` identifier?

No, as stated on our [Supported Actions](/queues/reference-content/queues-support/) page, Scaleway Queues do not currently support `MessageGroupid`.

To ensure strict message ordering, FIFO queues on Scaleway are designed to allow only one message to be in flight at a time per queue. Because of this, there is no concept of message grouping. If you are using a Serverless Function triggered by the queue, the system will only deliver one message at a time, limiting horizontal scaling, as concurrent processing of independent message batches is not possible.