queued message has insufficient lease time [SQL0105]

A queued message cannot start with enough lease time for its timeout, TimeoutGrace, and RecordMargin. Its range remains unresolved until reclaim; successful handlers in that range can repeat.

For example, charge-cards holds ids 1–4. If id 3 reaches dispatch with only 20 seconds left but needs a 30-second timeout plus recording and cancellation budgets, it does not run. The warning names that message, the range bounds, lease_remaining, and the required timing budgets.

Reduce both BatchLimit and QueueSize, raise QueueMargin to cover legitimate waiting, or increase MessageConcurrency when independent handlers and downstream capacity permit it. Ordered messages on one key stay serial. Raising the handler timeout and its ceiling together adds no queue allowance. See queue and lease budgets.

The warning is emitted once per locally tracked range; the instance’s shared suppression window can collapse warnings from further ranges.