CarlosJuncher03 opened a new issue, #6382: URL: https://github.com/apache/hop/issues/6382
### What would you like to happen? Description: Issue Type: Improvement / Feature Request Priority: Minor / Major (depending on urgency) Summary: The current REST Client transform attempts the HTTP request only once. If there is a network glitch, a timeout, or a temporary server error (e.g., HTTP 503 or 429), the transform fails immediately or sends the row to the error handling path. To handle transient failures, developers currently have to build complex workarounds using loops or child pipelines. It would be significantly more efficient to have a native retry configuration directly within the REST Client transform. Proposed Solution: Add a new tab or section (e.g., inside the "General" or a new "Options" tab) with the following fields: Number of Retries: (Integer) How many times to attempt the request again upon failure (e.g., 3). Retry Delay (ms): (Integer) The wait time between attempts (e.g., 1000 ms). (Optional/Advanced) Retry on Status Codes: A list of codes to retry on (e.g., 429, 500, 502, 503, 504). If left empty, it could default to retrying on any connection exception. Benefit: This enhancement would greatly simplify pipelines that interact with external APIs, making them more robust against network instability without requiring complex workflow logic. ### Issue Priority Priority: 3 ### Issue Component Component: Transforms -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
