Currently EDI jobs complete and then tables lock for updating to complete through out Alma. This leaves other similar jobs stuck in the queue as Pending for several minutes.
Under this change instead of a completed job that locks tables being moved directly to history it would get an additional status in the Running jobs area. This status would let users know that the job had completed, but that Pending jobs would not be starting.
We have had ongoing issues where staff confusion resulted from a job completing, but the next job staying in Pending for 2-10 minutes. After much consultation with support this proved to be because the previous completed job had locked processes on the backend. This lock was automatically lifted and the Pending processed started, but not until after the confusion had occurred.