Process-Level Timeout Configuration for Application and Component Processes

Hello everyone,

DevOps Deploy does not provide a mechanism to configure a timeout at the Application Process or Component Process level. When a process step becomes unresponsive, for example due to a hung startup script, network issue, database connectivity problem, or an external system dependency, the deployment can remain in a running state indefinitely and requires manual intervention.

We would like to request the ability to configure a maximum execution timeout for Application Processes and Component Processes.

Proposed functionality:

• Allow administrators to configure a timeout value at the Application Process level.
• Allow administrators to configure a timeout value at the Component Process level.
• The timeout should apply to all steps executed within the process.
• If the configured timeout is exceeded, the currently running step should be terminated and the process should fail automatically.
• Individual steps may optionally be allowed to override the process-level timeout if greater flexibility is required.

This request is specifically targeted at Application and Component Processes rather than the entire deployment request. Deployment requests may legitimately contain Manual Tasks that remain pending for many hours or until the next business day, whereas automated process steps should not be allowed to run indefinitely.

Example use case:

A startup script executed during deployment becomes unresponsive and never returns control to DevOps Deploy. With a process-level timeout configured to 180 minutes, the deployment would automatically fail after three hours instead of remaining stuck indefinitely.

Thank you all

Ales Bahnik