Skip to content

Commit 2d120ae

Browse files
committed
fix(mnq): add question to faq
1 parent f985290 commit 2d120ae

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

pages/queues/faq.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,10 @@ We currently implement the API endpoints listed [here](/queues/reference-content
2121

2222
## How is Scaleway Queues billed?
2323

24-
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/).
24+
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/).
25+
26+
## Do Scaleway FIFO queues support the `MessageGroupId` identifier?
27+
28+
No, as stated on our [Supported Actions](/queues/reference-content/queues-support/) page, Scaleway Queues do not currently support `MessageGroupid`.
29+
30+
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.

0 commit comments

Comments
 (0)