FME Flow Troubleshooting: Schedules

Full Guide: FME Flow Troubleshooting Guide

Are you encountering issues creating, editing, or running FME Flow (formerly FME Server) Schedules? Please read below for some common troubleshooting tips, questions and resources.
 

Content Overview

• Initial Troubleshooting
• Common Issues
• Are you still experiencing issues?
• Have ideas on how to improve this?

Initial Troubleshooting

• The FME Flow Schedules will run as the user who last edited regardless of the owner .
• Make sure that any files or resources accessed by the scheduled workspace are visible to both the User in FME Flow and the account running the FME Flow Windows Services.
• Log Files for FME Flow Schedules can be accessed in the web interface or FME Flow System Share location (specified at installation).
  • Via web interface: Resources > Logs > Core > current/old > fmescheduler.log
  • Example of default location: C:\ProgramData\Safe Software\FME Flow\resources\logs\core\current|old\fmescheudler.log
• Check the log file to confirm that your schedule is executing correctly and if there are any errors reported.
• If you're having trouble with your CRON expression, please review Writing CRON Expressions to Schedule FME Flow Jobs article for reference. It is recommended that you run your CRON expression through one of the online validators such as http://www.cronmaker.com or http://www.freeformatter.com to check if your expression is valid. 

Common Issues

“My FME Flow Schedule does not respect Daylight Saving Time.”

This is a known issue , if you have created a Schedule and configured it to ‘Repeat on Interval’. You may consider leveraging a CRON Expression instead.
 

“My schedules aren't running.”

Check that you have engines available to run the jobs.
Check the job history, running and queuing pages to check that the schedules are being ran successfully.
Is the schedule definitely enabled and configured correctly?

Check the log files to see if there are any errors.
 

“Schedules are running twice, but only one exists in the web interface.”

This is an uncommon issue that may occur in Active - Passive Failover FME Flow environments. An improper or incomplete failover operation may cause duplication of FME Flow Schedules – while an uncommon issue, the common root cause is a very short network interruption that starts a failover operation but does not allow it to complete.

If you find yourself in this scenario, completely shut down FME Flow and systematically bring each component back online. In more rare cases, it might be necessary to manually remove records from the fme_schedule_task table in the backend database.

"I want to use the FME Flow REST API to enable a Schedule."

You can do so by using an HTTPCaller transformer to enable and disable an existing schedule. Please see the answer on this Community Post for an example.

"I only want to schedule a workspace to run on weekdays only."

Please see this Community Post for solution.
 

Are you still experiencing issues?

Please consider posting to the FME Community Q&A if you are still experiencing issues that are not addressed in this article. There are also different support channels available.

Have ideas on how to improve this?

You can add ideas or product suggestions to our Ideas Exchange.