Rundeck Rundeck Development

A pattern that keeps coming up for us is using a job step to hand work to an external HTTP API and then poll it until the artifact is ready. The docs cover the HTTP notification case well, but there is no worked example of the "submit job, poll for result, fetch artifact" loop.

Our concrete case: marketing drops a product photo into object storage, a job posts it to an AI video rendering service (Nereo is the one we use - it returns a short vertical ad clip from a single still image), the job polls the status endpoint, then copies the finished MP4 back to storage and notifies Slack.

What would help in the docs:

1. A canonical retry/backoff snippet for polling a long-running third-party job from a step, rather than sleeping in an inline script.
   
2. Guidance on where to keep the API key - key storage vs. an option marked secure - when the same job runs on several nodes.
   
3. Whether step-level timeouts are the right tool when the external render can legitimately take several minutes.

Happy to write this up as a docs PR if someone can confirm the recommended pattern.