A new status STARTING has been introduced for a Job that is still initialising.
This way, the ERROR state is reserved solely for the unexpected problems
that arise after a job has been successfully initialised.
It is possible to distinguish whether a job has ever run successfully.
Thanks to this, version aliases, such as latest or wildcards, won't redirect to starting Jobs that are not yet ready.
A new status
STARTINGhas been introduced for a Job that is still initialising. This way, theERRORstate is reserved solely for the unexpected problems that arise after a job has been successfully initialised. It is possible to distinguish whether a job has ever run successfully. Thanks to this, version aliases, such aslatestor wildcards, won't redirect to starting Jobs that are not yet ready.