We are doing some testing with the RAK 3172 module and have noticed some unexpected behavior. We have the 3172 configured in Class A mode and are testing a workflow where the end node will send an uplink and receive a downlink queued on the Lora Network Server. In situations where multiple downlink messages are queued on the network server, the 3172 will receive all of the downlink messages in succession after a single uplink message. This is not expected behavior as defined in the Lorawan specs. We would expect at most 2 downlink messages(1 per receive window). We are using confirmed uplink messages and using AWS IoT Core for Lorawan for the backend/Lora Network server. This has been tested using confirmed and unconfirmed downlinks. This behavior has been observed on multiple different gateways running as Basics stations. Can someone explain why this behavior is occurring? Is there a configuration that we are missing?