It would be helpful to hear which variables would be most useful to everyone by adding them to the comments of this suggestion.
To be clear, do you mean the retry policy for an HTTP request (which includes the timespan between retries and the number of retry attempts to make)?
169 votesGuy Burstein responded
Thanks for the suggestion. We’re reviewing it.
Thank you for submitting this idea! This has been something that we have been considering but were waiting for customer feedback. In regards to your last question about overriding the feature could you provide more clarity as to what you are looking for?
KevinYohan S. commented
If I have 30 Jobs which will call the same API with the same credential It will be great to manage it from a JobCollection.
However If I have 5 different Jobs which will call, each ones, different APIs with different credentials, It would be great to have a JobCollection to store all of them and having the possibility to define credentials directly into Jobs instead of creating a JobCollection for each credential.
If you are going to make this change, It would be great to still keep the possibility to define credentials by Job.
ThanksYohan S. shared this idea ·