Related to: #335
We patched this in the Maintenance Tasks gem here, but this is reopening JobIteration's private API and is ideally something we should solve upstream if possible.
I attempted to write an upstream patch to do so on this branch, but ran into issues when testing against Core (see CI Build). There are a number of batch iteration jobs that depend on the reenqueue happening from within #iterate_with_enumerator, prior to the shutdown / after perform callbacks happen in order to gracefully retry from the last cursor if an error gets raised while processing a batch. The complexity level for these jobs is quite high, so it will need more investigation.
Related to: #335
We patched this in the Maintenance Tasks gem here, but this is reopening JobIteration's private API and is ideally something we should solve upstream if possible.
I attempted to write an upstream patch to do so on this branch, but ran into issues when testing against Core (see CI Build). There are a number of batch iteration jobs that depend on the reenqueue happening from within
#iterate_with_enumerator, prior to the shutdown / after perform callbacks happen in order to gracefully retry from the last cursor if an error gets raised while processing a batch. The complexity level for these jobs is quite high, so it will need more investigation.