To add to Don's comment. The product is doing exactly what it is supposed to.
READY state means job has been sent to Agent. Normally, as soon as WA Agent gets the job it runs it.
However, if job is stuck in READY and is not changing to to EXEC state, then something may have gone wrong.
There can be two main reasons for this (there can be others as well!):
1. Network issue.
2. Filesystem related issues in the agent (Unix/Linux agents).
Your job may be running or not. The manager/scheduler has no way to know what happened. Hence, the manager side clock will continue to run for the job and if overdue is set then it will (and should) send the overdue alert if the job has not completed.
Thanks,
Nitin Pande
Broadcom