The IFS .NET Access Provider is expected to support a timeout parameter, allowing users to configure how long a task should wait before timing out. However, this functionality is not currently implemented in Novacura's IFS10 connector. As a result, all long-running tasks time out after one minute, with no available option to extend this limit.

This limitation hampers the execution of tasks that take more than one minute to complete, making it impossible to include them in flows. This leads to inflexibility in designing complex workflows and might impede the completion of important business processes.

We propose implementing the timeout parameter within Novacura's IFS10 connector. By providing a way to configure the timeout duration for individual tasks, users can ensure that longer-running processes are given the necessary time to complete without interruption. This enhancement will provide greater flexibility in workflow design and ensure that all necessary tasks, regardless of execution time, can be included in flows.