bandicot

A usage limit pauses a run instead of failing it

When an account reaches its usage limit, the run now pauses with its reset time and a Continue, rather than failing with a red error and no reason.

Engine

When the model account hit its usage limit, a run used to stop with a red error and no reason, and anything you typed ahead was lost. Now the run pauses instead: it keeps its place, shows when the limit lifts, and offers a Continue. If another signed-in account of the same kind has room, the work moves there on its own.

A run that truly fails now always says why, in plain words, rather than leaving the reason blank.