It is possible to create a job with 0 retries (via default config), which then means that the job is never executed unless the retries are incremented. Additionally, an incident is immediately raised.
Current behavior:
- No incident message
- This can be a mistake in development (as retries here basically means tries) leaving people wondering why an incident is raised.
Expected behavior:
- The incident message should say that the job was initially created with zero retries. This allows developers to quickly detect the mistake
Additional thoughts:
- it would maybe also be nice to have such a message when retries are set to 0 via API