FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
ssanga
Staff & Editor
Staff & Editor
Article Id 350821
Description

This article describes how to resolve an issue in the FortiGate GUI where the automation stitch is grayed out when the trigger is set to a schedule.

Scope

FortiGate v7.2.8, v7.4.4, v7.6.0.

Solution

When an automation stitch is configured with a ‘scheduled’ trigger-type, the test automation stitch option in the GUI appears grayed out. However, the automation stitch can still be tested successfully via the CLI.

 

Sample config:

 

config system automation-action

    edit "Action"

        set action-type cli-script

        set script "execute backup full-config sftp Fortigate/FW001%%date%%.cfg < ip address > < username > < password >"

        set accprofile "super_admin"

    next

end

 

config system automation-trigger

    edit "Trigger"

        set trigger-type scheduled

        set trigger-hour 8

        set trigger-minute 45

    next

end

 

config system automation-stitch

    edit "Stitch"

        set trigger "Trigger"

            config actions

                edit 1

                    set action "Action"

                    set delay 30

                    set required enable

                next

            end

        next

    end

 

Navigate to Security Fabric -> Automation -> Right-click on the configured stitch to find 'Test Automation Stitch' grayed out.

 

TestAutomationStitch.png

CLI:

 

diagnose automation test Stitch

automation test is done. stitch:Stitch

 

This issue has been resolved in FortiOS versions 7.2.9, 7.4.5, 7.6.1.

Workaround:

Test the automation stitch using the following CLI command:

 

diagnose automation test <Stitch_Name>

 

Logs required by FortiGate TAC for investigation:

  1. The configuration file of the FortiGate.
  2. Fortinet Support Tool Data.
  3. The output of the following command:

diagnose automation test <Stitch_Name>

 

  1. The output of the following command:

 

execute tac report