Troubleshooting Tip: FortiProxy does not execute CLI script by triggered automation stitch

A v7.4.13 FortiProxy with a configured daily schedule trigger has a CLI script that should disable policy 1. A snippet of the commands is provided below:

config system automation-stitch
    edit "test"
        set trigger "schedule"
            config actions
                edit 1
                    set action "disable_policy"
                    set required enable
                next
            end
        next
    end

config system automation-trigger
    edit "schedule"
        set trigger-type scheduled
        set trigger-hour 10
        set trigger-minute 57
    next
end

config system automation-action
    edit "disable_policy"
        set action-type cli-script
        set minimum-interval 2
        set script "config firewall policy
            edit 1
                set status disable
            next
        end"
        set accprofile "super_admin"
    next
end

Even though the CLI script is called to be executed, the firewall policy remains enabled:

2026-03-04 10:57:08 [symlink_config_file:425] '/data/./config/sys_global.conf.gz' has been symlink'ed to the new version '/data/./config/sys_global.conf.gz.v00000
0036'. The old version '/data/./config/sys_global.conf.gz.v000000035' has been deleted
2026-03-04 10:57:09 zip config file /data/./config/sys_global.conf.gz success!

2026-03-04 10:57:06 __action_cli_script_open()-190: cli script action:disable_policy is called. svc ctx:0x55e0c7af8dc0
accprof:super_admin script:
config firewall policy
    edit 1
        set status disable
    next
end

The trigger count on the GUI shows that the stitch is implemented. However, the CLI script is not implemented. As per the internal investigation, this is unexpected behavior. The issue is scheduled to be fixed in 7.4.14, which is scheduled for a release around 27th of May (this date is provisional and it can be moved back/forward).