Chakra UI toast queue management without native priority ordering

The useToast hook in Chakra UI manages notifications by stacking based on arrival time. While the id prop effectively prevents duplicate instances of the same event, the system lacks a native mechanism to define importance or priority levels for concurrent alerts.

When high-frequency events trigger multiple notifications—such as critical system errors alongside routine status updates—the toasts follow a strict chronological order. This can lead to visual noise where critical information is pushed out of the viewport or buried under less-priority auto-dismissing alerts.

Is there a configuration option to implement a priority-based queue that ensures specific statuses remain at the top of the stack? Additionally, can the toast container dynamically reorder existing instances without triggering the internal exit animation logic?