Use the Configuration > Script Schedules tab to manage script schedules performed on databases hosted by FileMaker Server. Use this tab to create new schedules, edit existing schedules, and enable or disable schedules. Scheduled tasks run automatically when they are enabled.
See Scheduling administrative tasks for an overview of script schedules.
Detail | Description |
Schedule name | The name of the schedule |
Database | For FileMaker scripts, the database that contains the script |
Scheduled time | The next time the schedule will run. This column may also display Running when a schedule is running or Disabled if there are no more valid times for the schedule to run. |
Enabled | Whether the schedule is enabled to run automatically |
To | Do this |
Create a script schedule | |
View script schedule details | Select a script schedule and click Settings. |
Enable or disable a script schedule | Set the script schedule to Enabled or Disabled. |
Rename a script schedule | |
Duplicate a script schedule | Select a script schedule and click Duplicate. |
Delete a script schedule | Select a script schedule and click Delete. |
Run a script schedule | Select a script schedule and click Run Now. |
Admin Console allows you to save your schedules to a settings file and load the settings file to restore previously saved schedules. See Saving and loading schedules.
•A new script schedule is enabled by default if its next run time is valid.
•FileMaker Server adds entries in the Event.log file when a scheduled task runs. See Viewing log file entries.
•FileMaker Server puts tasks and file-related commands from Admin Console and the CLI into the following separate queues:
•Backup, verify, and file-related commands (for example, open, close, pause, and resume): Only one task or command runs at one time from this queue. The remaining tasks or commands are delayed until the current one is complete.
•Send message and run script schedules (FileMaker scripts and system script files): Multiple tasks can run at the same time from this queue.
FileMaker Server runs tasks from both queues at the same time. For example, the first queue has a backup command and a pause command. The second queue has a script schedule. FileMaker Server runs the backup command and script schedule at the same time. The pause command is not run until the backup command completes.