Editing automation rules options

If Helix ALM Server performance or cache locking issues occur when running executables from triggers or escalation rules, you can change the number of seconds before executables time out and the maximum number of simultaneous processes that can run per project .

1. Click Server Options.

The Edit Server Options dialog box opens.

2. Click the Automation Rules tab.

3. Make any changes.

Field	Description	Default value
Pre-Save Triggers
Timeout executables after X seconds	Indicates how often theserver should time out executables running from triggers that run before items are saved to the database.	30 seconds
Post-Save Triggers
Timeout executables after X seconds	Indicates how often the server should time out executables running from triggers that run after items are saved to the database.	60 seconds
Maximum simultaneous processes allowed per project	Maximum number of processes that can run from triggers at the same time per project on the server.	20 processes
Escalation Rules
Timeout executables after X seconds	Indicates how often the server should time out executables running from escalation rules.	60 seconds
Maximum simultaneous processes allowed per project	Maximum number of processes that can run from escalation rules at the same time per project on the server.	40 processes
Webhooks
Timeout webhook connection attempts after X seconds	Indicates how long Helix ALM waits for the connection to be established to the recipient.	5 seconds
Timeout webhook requests after X seconds	Indicates how long Helix ALM waits for the recipient to respond that it has received the webhook.	10 seconds

4. Click OK to save the changes.