bug
Queue strategy is being ignored when sending an array of messages to rpcCallRequest node.

Server Environment

• own setup
  • docker deployment
  • ThingsBoard 3.2.2CE/PE

Client Environment

• OS: OSX, node app

• Connectivity

  • MQTT
  • Gateway

To Reproduce
Steps to reproduce the behavior:

1. generator node with array of numbers
2. pass the message to checkpoint node (SequentialByOriginator)
3. connect this not to script node that loops over the array and create message objects which are passed as array to rpcCallRequest node

Expected behavior
Messages incoming on client in incremental order.
Messages incoming one at a time, next message arrives only if client published response with requested

Actuall behavior
Messages incoming on client in random order.
Messages incoming all at once regardless of whether client published response with requested or not

Screenshots

Additional context
The idea is to send multiple chunks to the device via gateway since the throughput between the gateway and the device does not allow to send large packages. Throwing chunks onto the sequential queue should result in messages being sent in the same order as they were in the array, one by one, only after the previous rpc call was confirmed by the gateway. Unfortunately the opposite is the case, the order is random, and if no confirmation on topic v1/devices/me/rpc/response/requestId happened all messages are still sent out.

Maybe there is another way how to put multiple messages on a queue at one go, the one way that I've found (send array) seems to ignore strategy. Am I doing something wrong or is it a bug?
Thanks!