That's a configuration file configuration. If we make have to make changeable through a service api call, then we would have to store the value in the DB. I don't think that is necessary. Do you?
True. But, what happens if a particular job has repeatedly failed, e.g., because of an external service being unavailable, and the configured number of retires has been exceeded. When the service is online again, would an operator have to increase the number of retries for the failed job manually in the according database table or will there be an API or even a front-end for restarting it?
Such jobs end up in a special job error table. These jobs can then manually be retried. That list and the retry functionality still need to be implemented in the UI though.