Schedule a Workspace to Run with FME Server

Liz Sanderson
Liz Sanderson
  • Updated

FME Version

  • FME 2022.2


FME Server Schedules provide a simple way to run a workspace at a defined recurrence. This tutorial will guide you through creating a basic schedule. If you need to schedule a more complex workflow that involves multiple workspaces, please see Schedule a Workspace to Run with FME Server Automations


It is recommended that you complete the first three exercises of the Tutorial: Getting Started with FME Server, so that you can become familiar with publishing a workspace and uploading data to FME Server.


In this tutorial, we’ll create a daily schedule to run the CommunityMapping.fmw workspace, which will read layers from a file geodatabase and write them out to our chosen shp file format.

Step-by-Step Instructions

1. Publish the Workspace and File Geodatabase
As demonstrated in the Tutorial: Getting Started with FME Server, publish the communitymapping.fmw and communitymap.gdb to FME Server. The geodatabase is included within the communitymapping.fmwt template that is part of the files at the top of this article. 

2. Create a New Schedule
From the FME Server Web User Interface, click Build Schedule.

On the Create New Schedule page, enter:
  • Name: CommunityMapping
  • Category: Production (note: type to create the new category)
  • Description: “Daily schedule to create .shp files from communitymap geodatabase"
  • Enabled: checked
  • Schedule Type: Basic
  • Recurrence: Daily
  • Date Range: Leave defaults (current date and time, no end, does not expire. Note that the time chosen as the Date Range start is the time when the schedule will run each day, based on the time zone of the FME Server).
  • Skip if Job In Progress: unchecked (note: this setting is useful for long-running jobs)

In the Workspace section, choose:
  • Repository: <the repository you published the workspace to>
  • Workspace: CommunityMapping.fmw
  • Enter an output format (optional): Esri Shapefile
  • Feature Types to Read (optional): <select all>
If desired, notifications can be set up to send upon successful or unsuccessful execution of the schedule. Also, queue routing and job expiry can be configured in the Advanced settings. We’ll leave these for now. Click OK.

3. Test the Schedule
The schedule has now been created and appears in the list. To test it without waiting until tomorrow, manually trigger the schedule by selecting it and choosing Trigger from the Actions menu.

To confirm the schedule ran successfully, click Jobs and check the Status of the CommunityMapping workspace.

The job has completed successfully.

The CommunityMapping workspace will now run at the next scheduled time 
If this was a real schedule, you would also want to consider sharing it with other roles and users from the Manager Schedules page.

Additional Resources

Was this article helpful?



Please sign in to leave a comment.