Scheduling administrative tasks
FileMaker Server can run multiple administrative schedule automation tasks:
FileMaker scripts defined in hosted databases; see Running FileMaker scripts
system script files; see Running system script files
database integrity verification; see Running database verification
FileMaker scripts, system scripts, and database verifications run on the primary machine in your FileMaker Server deployment.
To run a schedule, create a scheduled task on FileMaker Server. Specify the task type, and when and how often to run the task. See Creating or changing a script schedule. As with any schedule, you can run the scheduled task manually at any time. See Running a script schedule manually.
While a schedule is running, the Scheduled Time column changes to Running. Immediately after the schedule completes, the column temporarily changes to either Succeeded or Failed to indicate the result. For detailed information about the schedule, review the
Event.log messages that have been logged. See Event log.
You can create a script sequence scheduled task that runs pre-processing and post-processing system scripts before and after a FileMaker script. See Creating script sequence tasks.
In addition to these schedules, FileMaker Server also supports the following schedule types:
backup schedules; see Scheduling database backups
message schedules; these schedules can be created using the FileMaker Admin API or imported from a prior version of FileMaker Server
To create schedules using the FileMaker Admin API, see the FileMaker Admin API reference files in the Documentation folder:
FileMaker Server only, Windows:
[drive]:\Program Files\FileMaker\FileMaker Server\Documentation
If FileMaker Server is installed in a non-default location, the beginning portion of the default path shown above,
\Program Files\FileMaker\FileMaker Server, is replaced with the path that was specified during installation. For example:
FileMaker Server only, macOS:
FileMaker Server only, Linux:
Claris Server only, Linux: