Update pages/queues/faq.mdx

Co-authored-by: Rowena Jones <[email protected]>

Author: jcirinosclwy

pages/queues/faq.mdx

@@ -27,4 +27,10 @@ Billing is based on [queue volume](/queues/concepts/#queue-volume) - the combine
 
 ### Is the Scaleway Queues gateway compatible with my application, framework, or tool?
 
-We currently implement the API endpoints listed [here](/queues/reference-content/queues-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including [KEDA](https://keda.sh/) and [Symfony](https://symfony.com/). Note that you need to specify both Regions and URL to ensure compatibility.
+We currently implement the API endpoints listed [here](/queues/reference-content/queues-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including [KEDA](https://keda.sh/) and [Symfony](https://symfony.com/). Note that you need to specify both Regions and URL to ensure compatibility.
+
+### 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.