This article describes how to restart the WAD process with a specific day of the week (e.g. Monday, Wednesday, Friday) and specific time (e.g. 2:00 AM). This can be an effective workaround when there is a memory leak on the WAD process. There are different methods on an automatic restart of WAD: Auto-script (based on Interval) and wad-restart-mode memory (based on the used memory). The method in this article is to specify the day of the week and time.
v7.0, v7.4.
config system automation-trigger
edit "Monday_2AM"
set trigger-type scheduled
set trigger-frequency weekly
set trigger-weekday monday
set trigger-hour 2
set trigger-minute 15
next
edit "Wednesday_2AM"
set trigger-type scheduled
set trigger-frequency weekly
set trigger-weekday wednesday
set trigger-hour 2
set trigger-minute 15
next
edit "Friday_2AM"
set trigger-type scheduled
set trigger-frequency weekly
set trigger-weekday friday
set trigger-hour 2
set trigger-minute 15
next
end
config system automation-action
edit "wad_restart"
set action-type cli-script
set script "diag test app wad 99"
set accprofile "super_admin"
next
end
config system automation-stitch
edit "Monday_2AM_Restart"
set trigger "Monday_2AM"
config actions
edit 1
set action "wad_restart"
set required enable
next
end
next
edit "Wednesday_2AM_Restart"
set trigger "Wednesday_2AM"
config actions
edit 1
set action "wad_restart"
set required enable
next
end
next
edit "Friday_2AM_Restart"
set trigger "Friday_2AM"
config actions
edit 1
set action "wad_restart"
set required enable
next
end
next
end
Navigate to Security Fabric -> Automation. The trigger count will increment if the script was executed.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.