Description
Currently, the retrying mechanism in transform is tightly tied to the scheduling, i.e. the retry happens every configured frequency.
We could decouple scheduling from retrying by introducing a wrapper around SchedulerEngine that would both schedule transform task on frequency as well as on a retry event.
This requires some refactoring.
Description
Currently, the retrying mechanism in transform is tightly tied to the scheduling, i.e. the retry happens every configured
frequency.We could decouple scheduling from retrying by introducing a wrapper around
SchedulerEnginethat would both schedule transform task onfrequencyas well as on a retry event.This requires some refactoring.