@Ivan Tioh Thanks for reaching out.
When you scheduled the message the state of the message is Scheduled
but it still resides on the queue/topic and the schedule message will add to the total limit. As the message is not in the active state the client doesn't consume those messages. Scheduled messages and their sequence numbers can also be discovered using message browsing.
Once the enqueue scheduled time UTC clicks in then the jobs running at the backend changes the state of the message from Scheduled to Active state. Once the message becomes active in case of topic the messages will now be forwarded to all the subscription and based on the filter condition the subscription will accept/discard those message. In case of queue the message is visible when the state changes to active and now your client can consume those messages from queue/subscription.
For more details on schedule messages, you can refer to this document. Feel free to get back to me if you have any queries or concerns.