[Bug / Feature Request] Pause queue execution when 5-hour rate limit is reached

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.611.62324 • Released 17 cze 2026

What subscription do you have?

Pro

What platform is your computer?

win x64

What issue are you seeing?

I schedule a sequence of messages/tasks in a queue to be executed one after another.
When the 5-hour message limit is reached, the app does not pause the queue. Instead, it instantly dumps and sends all remaining queued messages at the exact same time. This breaks the intended sequential workflow and wastes requests.

What steps can reproduce the bug?

Steps to reproduce

1. Add a sequence of multiple messages (e.g., 5-10 tasks) to the execution queue.
2. Run the queue continuously until you hit the 5-hour rate limit.
3. Observe the queue behavior the exact moment the limit is triggered.

Explanation

The application fails to catch the rate-limit error correctly to pause the execution. Instead of halting the loop, the error triggers an immediate flush, causing all remaining queued messages to blast out at the same time.

What is the expected behavior?

Add an option (enabled by default): "Pause queue on rate limit".

• When limit is hit: The app should automatically pause the execution queue.
• When limit resets (after 5 hours): The app should automatically resume sending the queued messages one by one, maintaining the original planned sequence.

Additional information

Why this matters

Currently, hitting the rate limit unexpectedly ruins the planned conversation flow and automated workflows. Pausing the queue until the limit resets ensures data consistency and saves API/message usage.