Downlink queue, order of send for confirmed messages

Hi everyone,
assuming I stack multiple (using schedule:last) confirmed downlink messages (in my case for a LoRaWAN e-ink display). Would the backend try to keep sending that very same message in the queue until the corresponding ack was received and only then move to the next message in the queue?