Http connector response timeout in action

We are currently encountering response timeout errors when executing Moveworks actions, particularly when calls to external systems take longer than expected. On testing these endpoints with Postman, we observe that responses are received, but sometimes after more than 60 seconds. The inability to configure timeout duration dynamically is causing integration challenges and reliability issues.

We propose introducing a feature that allows for a separate configuration file, where timeout values can be easily increased or decreased as needed. This would enable teams to optimize and test timeouts based on the performance of integrated external systems, thereby minimizing timeout errors and improving overall flexibility.

Implementing dynamic timeout configuration would help ensure smoother operations for a variety of use cases. Could this feature be considered for future releases?