Contradictory message states ("Not sent" vs. "Queued") and displaced error message

Summary:

With SAP Business One and Outlook connected to the chat, a request failed with "The chat service is temporarily unavailable. Please try again in a moment." The failed message was marked "Not sent" - yet the immediately following message was accepted into a queue ("Queued · #1"), implying background processing was still ongoing. This contradicts the "not sent" state. After the queue processed, the error message was re-positioned below the later messages, breaking the timeline order.

Original Error and “Queued“ message:

Error Message moved:

Expected Result:

• Message states should be consistent: if the service can queue subsequent messages, the failed message should not be labeled "Not sent".

• The error message should remain in its original chronological position.