How to configure retries on OTA jobs on the IoT Core

Hi Giovanni. Retry configuration is currently not supported by CreateOTAUpdate. So you can not do it, in one step, from the console, the CLI, or the SDKs.

it makes no sense to do it this way since the template its based on a ota job that its executing or has already been executed

If you want to do it all from the console, the template method is currently the only way. You could create a dummy thing in the registry, and create an OTA update job that targets it. Then cancel the job. Then create a template from the job, adding retries. Ugly, but it will work.

If you are willing to use SDKs or the CLI, you can construct the OTA job document yourself. An OTA update is really just a job with a predefined job document. A call to CreateOTAUpdate will also call CreateJob. If you use MQTT protocol, and sign the file, CreateOTAUpdate may (depending on what options you use) additionally call StartSigningJob and CreateStream. This is the magic of CreateOTAUpdate; it bundles all this into one (complex) operation. However, you could do these calls yourself to create and obtain the stream name and signature to use in the job document. Then create the job document.

Once you have the job document, you can call CreateJob or CreateJobTemplate. Or indeed return to the console to use the job document.