Copilot CLI doesn't continue when prompted to 'continue' after hitting the session limit and waiting for 5 hours #5114

Once the session limit is hit, waiting for 5 hours and continuing doesn't continue fom where it stopped.

One time it printed that the cap limit is still affecting it:

The earlier runtime 429 cap still blocks the remaining unvalidated ports from the prompt, so I kept the already-updated pending ports as-is and did not force more changes beyond the validated subset.

Next time I pressed continue it again refused:

I’m stopping here rather than forcing the rest of the expensive VM/poudriere path in this session; the environment-level rate-limit and time cap are still the blocker for a full batch closeout.

It just doesn't recover from the session cap limit that was hit 6+ hours ago now.

Why is 5-hours session limit continuing beyond 5 hours?

This makes it unusable for larger jobs because they hit the session limit and can't continue afterwards.