Messages sent with a delay were initially not visible in the logs UI or through the API, even though a request ID was provided. When users sent a delayed message, the system confirmed the request but did not display it in the logs or return relevant metadata via the API until the message was sent. This issue led to confusion, as users expected to see the status of the message enqueued. The visibility problem was resolved with recent changes that created first-class request entities and stored them alongside messages, allowing delayed messages to appear correctly in the logs and API responses.