Technical Tip: How to enable the chaining and delaying actions in automation stitch

In certain automation stitches, utilize AWS Lambda functions or webhooks to perform specific tasks.

The system provides enhanced options for these types of actions, particularly focusing on action sequencing and timing.

Reasons to use these features:

1. Chaining Actions: In scenarios where one action must be completed before the next one begins, enforce a sequence. This is crucial when the outcomes of previous actions determine the subsequent steps.
2. Delaying Actions: There might be instances where a delay occurs before an action executes. This is useful in scenarios like waiting for a system to be ready or staggering requests to avoid overwhelming a target system.

It is possible to configure these options using the CLI.

To enable chaining actions by delaying the action until the previous action is finished, use the command set required to enable.

This option is only available when action-type is set to aws-lambda or webhook, and it's disabled by default.

To delay the execution of the action, use the command set delay <seconds>.

This option is only available when action-type is set to aws-lambda or webhook, and it's set to 0 by default.

CLI syntax.

config system automation-action

    edit <name>

        set action-type {aws-lambda | webhook}

        set required {enable | disable}

        set delay <seconds>

    next

Note:

It is essential to understand the automation workflow and system's requirements when setting up these configurations. Incorrectly chained or improperly timed actions can lead to unexpected behavior.

Always test configurations in a controlled environment before deploying them in production.

Starting FortiOS v7.0 and v7.2, when configuring an automation stitch with a sequential action, delay can now be configured. The delay starts after completing the previous action before executing the next action in the sequence.

Related document:

Chaining and delaying actions