Please update the EDD to be explicit regarding what happens to other jobs in an equivalence class if a job is scheduled to run but the job run event is rejected by the server (for example, a runjob hook rejects the action).
I’ve made a small update to the EDD. This is due to a bug that was fixed in the feature post-checkin (PP-828). A suspended job could cause other jobs to not run even though they could. This was due to the fact that a suspended job has a select statement generated for it based on the original select statement and the vnodes the job is running on. This will highly likely result in each suspended job to be placed into its own equivalence class. The only case where multiple suspended jobs would be placed in the same class is if two jobs equivalent jobs are sharing the same vnodes.