FileMaker Server schedules allow scripts and administrative tasks to run automatically at predefined times.
A schedule can execute a FileMaker script stored in a hosted custom app, run a system-level script on the server, or combine both in a script sequence.
Schedules are commonly used for recurring operations that should not depend on a user opening FileMaker Pro and starting a script manually.
What is a FileMaker Server schedule?
A schedule is a task registered in FileMaker Server. It defines:
- What should be executed
- When it should start
- Whether it should repeat
- Which account should be used
- Which parameters should be passed
- Whether a timeout should be applied
Schedules can run once, every day, on selected days of the week, or at another defined interval. A daily schedule can also repeat several times between a starting and ending time.
Administrators manage schedules from the Configuration > Schedules section of the FileMaker Server Admin Console. A schedule can also be run manually, disabled temporarily, duplicated, edited, or deleted.
FileMaker script schedules
A FileMaker script schedule runs a script stored in one of the databases hosted by FileMaker Server.
When configuring it, the administrator selects:
- The hosted database
- The FileMaker script
- The FileMaker account used to run it
- An optional script parameter
- The execution time and recurrence
- An optional timeout
The script is executed by the FileMaker Server Script Engine, also known as FMSE or historically SASE.
Typical uses include:
- Processing new orders
- Creating invoices
- Importing or exporting information
- Synchronizing an external service
- Sending emails or notifications
- Generating reports
- Archiving completed transactions
- Updating aggregated data
- Performing overnight maintenance
Because the script runs on FileMaker Server, it does not require FileMaker Pro to remain open on a workstation.
A separate server-side session
Each scheduled FileMaker script runs in its own server-side session.
It does not inherit a FileMaker user’s current layout, record, found set, variables, or other interface context. The script must establish everything it needs to perform its task.
This generally means selecting an appropriate layout, finding the records to process, and interpreting any information supplied through the schedule’s script parameter.
The schedule also specifies the FileMaker account under which the script runs. That account and its privilege set determine what the scheduled process is allowed to see and modify.
A script that works correctly when started manually in FileMaker Pro will not necessarily work correctly as a schedule. Developers must verify that every script step is compatible with FileMaker Server and that the script does not depend on user interaction.
System script schedules
FileMaker Server can also schedule scripts executed directly by the server’s operating system.
Depending on the platform, these may include shell scripts, Windows batch files, PowerShell or VBScript scripts, and other supported system-level scripting technologies.
System scripts can perform operations outside the FileMaker database environment, such as:
- Moving or renaming files
- Preparing files for import
- Compressing exported documents
- Calling operating-system utilities
- Transferring files to another service
- Starting an external processing tool
- Performing infrastructure-related maintenance
These scripts run on the primary FileMaker Server machine. They must be placed in the appropriate FileMaker Server Scripts directory and executed with an operating-system account that has the necessary permissions.
Unlike a FileMaker script, a system script does not use FileMaker layouts, records, calculations, or script steps. It operates at the level of the server’s operating system.
Access to system scripts may therefore be restricted on managed hosting platforms for security reasons.
What is a FileMaker script sequence?
A script sequence combines a FileMaker script with one or two optional system scripts:
- A pre-processing system script
- A FileMaker script
- A post-processing system script
This allows a single schedule to coordinate operations both inside and outside FileMaker.
For example, a sequence could:
- Download, decrypt, or reformat a file using a system script.
- Import and process its contents using a FileMaker script.
- Compress or transfer the resulting files using another system script.
Another sequence might prepare a folder, ask FileMaker to generate a collection of reports, and then upload those reports to an external service.
Without a sequence, these operations would require separate schedules or a custom mechanism to coordinate them.
Success and failure in a sequence
The stages of a script sequence are dependent on one another.
The pre-processing system script must complete successfully before FileMaker Server proceeds to the FileMaker script. A successful system script normally returns an exit value of 0.
The FileMaker script must then complete successfully before the post-processing script is started.
This prevents later stages from proceeding when an earlier operation has failed. For example, FileMaker should not attempt to import a file if the pre-processing script was unable to prepare it.
Each stage should therefore implement proper error handling and produce useful log information.
Parameters and credentials
A schedule can provide a parameter to the FileMaker script. The parameter is passed as text and can contain a simple value or structured information such as JSON.
This makes it possible to reuse the same FileMaker script for several schedules. For example, one schedule might request the processing of invoices while another uses the same script to process credit notes, with the required operation identified in the parameter.
Credentials must also be handled carefully.
A FileMaker script schedule uses the database account configured in the schedule. System scripts use an operating-system account with access to the required files and commands.
These accounts should receive only the privileges required for their tasks. Password changes must also be reflected in the schedule, or the automated operation may suddenly stop working.
Monitoring scheduled tasks
An enabled schedule runs automatically according to its configuration. The FileMaker Server Admin Console displays its next execution time and indicates when it is running.
After execution, FileMaker Server reports whether the schedule succeeded or failed. More detailed information is written to the server log files, particularly Event.log and the script-related logs.
Reliable automation should not depend solely on an administrator occasionally opening the Admin Console. Important schedules should report their own result, record the beginning and end of each operation, and generate an alert when a process fails.
This is especially important for processes such as invoicing, data exchange, backups to external systems, or synchronization with third-party services. A schedule that silently stopped working several weeks ago can be more dangerous than one that fails visibly.
Schedules and server resources
Several script schedules can run at the same time. They may also run alongside backups, WebDirect sessions, Data API calls, OData requests, and scripts launched through Perform Script on Server.
Scheduled scripts therefore consume the same server resources used by the hosted applications and their users.
A schedule that processes thousands of records, generates large files, or calls a slow external API can affect the performance of the server. The time at which it runs, the number of concurrent schedules, and the efficiency of its scripts must all be considered.
FileMaker Server 2026 can use multiple SASE processes to increase server-side script throughput. This can allow more scripts to run concurrently, but it does not make inefficient scripts harmless. Greater concurrency may also generate greater CPU, memory, disk, and database activity.
Schedule settings belong to FileMaker Server
Schedules are configured in FileMaker Server, not stored inside the FileMaker database.
Moving a database file to another server does not automatically recreate its schedules. The new server must also receive the corresponding schedule configuration.
FileMaker Server can save and load schedule settings, which is useful when reinstalling or migrating a server. However, loading a schedule settings file replaces the schedules already configured on the destination server rather than merging the two sets.
Database paths, script files, accounts, permissions, and other dependencies should always be verified after a migration.
This is one reason why a FileMaker deployment cannot be fully migrated by copying only its .fmp12 files.
Schedules are part of the application
Although schedules are configured in FileMaker Server, they often perform essential business functions. They should therefore be treated as part of the application architecture.
Professional management includes:
- Documenting every schedule and its purpose
- Using clear and consistent names
- Recording dependencies and credentials
- Checking FileMaker Server compatibility
- Implementing structured script results
- Logging the start, completion, and failure of each operation
- Avoiding overlapping executions when they are unsafe
- Testing schedules after an application or server upgrade
- Including schedule configuration in migration plans
- Monitoring critical processes automatically
A schedule should never become an undocumented process that nobody notices until it stops working.
FileMaker schedule expertise from fmcloud.fm
At fmcloud.fm, we understand that hosting a FileMaker application involves much more than keeping its database files open.
Our team can help design, deploy, monitor, and troubleshoot FileMaker Server schedules, FMSE processes, system scripts, and script sequences. We can also help determine whether a process should use a schedule, Perform Script on Server, OData, the Data API, or an external automation service.
This combined FileMaker and server expertise is particularly valuable when automated processes are slow, overlap unexpectedly, fail without notification, or depend on resources outside the FileMaker application.
For business-critical applications, reliable scheduling is an essential part of reliable hosting.
Learn more
- Scheduling administrative tasks
- Using the FileMaker Server Schedules tab
- Running scheduled FileMaker scripts
- Running system script files
- Creating script sequence tasks
- Saving and loading schedule settings
- What Is the FileMaker Server Script Engine?
- What Is the FileMaker Command-Line Tool?
- What Is the FileMaker Server Admin API?
