A data engineering team runs a daily AWS Glue ETL job that ingests data from a third-party REST API. Roughly once a week the job fails because the API returns an intermittent HTTP 503 error during the first few minutes of execution; re-running the job manually always succeeds. The team wants to reduce operational overhead and recover automatically from these transient failures without rewriting the job logic. What is the MOST operationally efficient solution?