You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/message-sequencing.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,10 +47,14 @@ The **SequenceNumber** for a scheduled message is only valid while the message i
47
47
48
48
Because the feature is anchored on individual messages and messages can only be enqueued once, Service Bus doesn't support recurring schedules for messages.
49
49
50
+
> [!NOTE]
51
+
> Message enqueuing time doesn't mean that the message will be sent at the same time. It will get enqueued, but the actual sending time depends on the queue's workload and its state.
52
+
50
53
## Next steps
51
54
52
55
To learn more about Service Bus messaging, see the following topics:
53
56
54
57
*[Service Bus queues, topics, and subscriptions](service-bus-queues-topics-subscriptions.md)
55
58
*[Get started with Service Bus queues](service-bus-dotnet-get-started-with-queues.md)
56
59
*[How to use Service Bus topics and subscriptions](service-bus-dotnet-how-to-use-topics-subscriptions.md)
0 commit comments