FortiSwitch standalone mode automation not working in 7.6.6

Hi everyone,

I’m currently testing automation-based configuration backups to my SFTP server.

This setup works correctly on FortiSwitch 7.4.8,

but after upgrading to 7.6.6, the automation no longer completes successfully — with the same configuration and the same SFTP server.

Below are the configuration and logs for reference.

Config:

config system automation-trigger
edit "backup"
set trigger-type scheduled
set trigger-hour 10
set trigger-minute 40
next
end

config system automation-action
edit "backup"
set action-type cli-script
set script "execute backup config sftp %%log.date%%_FSW-124F_Backup.conf [my sftp server ip] [account] [password]"
set accprofile "super_admin"
next
end

config system automation-stitch
edit "backup"
set trigger "backup"
set action "backup"
next
end

Logs:

7.4.8:

FSW-124F # execute log display

1: 2026-01-20 10:40:23 log_id=0103030515 tz=+0800 type=event subtype=system pri=notice vd=root user="unknown" ui=auto-script action=backup msg="User unknown backed up the configuration from auto-script"

2: 2026-01-20 10:40:21 log_id=0103042580 tz=+0800 type=event subtype=system pri=notice vd=root stitch="backup" trigger="backup" action="backup" from=scheduled msg="stitch:backup is triggered."

7.6.6:

FSW-124F # execute log display
1: 2026-01-20 11:02:51 log_id=0103042521 tz=+0800 type=event subtype=system pri=information vd=root user="unknown" ui=autod action=stop msg="User unknown stop script autod.0 from autod"

2: 2026-01-20 11:02:51 log_id=0103042580 tz=+0800 type=event subtype=system pri=notice vd=root stitch="backup" trigger="backup" action="backup" from=scheduled msg="stitch:backup is triggered."

On 7.6.6, when the automation stitch is triggered, an additional log appears:

"User unknown stop script autod.0 from autod"

After this message, no configuration file is generated on the SFTP server.

Question:
Is this a known behavior change or restriction in FortiSwitch 7.6.x regarding automation CLI scripts or SFTP backups?
Are there any additional permissions, syntax changes, or limitations introduced in 7.6.6 that could cause the script to be stopped immediately?

Any insight would be greatly appreciated. Thanks in advance!