Scheduling Job on FME Server 2016

I created a workspace and tested it in FME Desktop.

Then published it to FME Server and tested it again.

Created a schedule to run the job this morning (and every day) at 07.00 (it is now 08.10).

Next I edited the workspace, tested and republished it (no changes to parameters).

Checked the schedule and it was still valid and enabled.

But no jobs where executed at the scheduled time (no passes and no failures).

My machine was locked and running (no shutdown).

Any suggestions why my job has not run?

Page 1 / 1

Anything inside the log-files?

Does the job appear as queued or running? Or did never get submitted it all?

The issue was solved after recreating the schedule.

I still don't have a clue why it did not run in the first time.

It did not even start, so no entries in any log files.

Does the job appear as queued or running? Or did never get submitted it all?

@kenbragg The job never got submitted. And I checked the date and time more than once. After recreating the job ran this morning without problems.

But again this morning the schedule was not executed.

I changed it to 10.00 AM yesterday and FME server executed the job (Succeeded.)

I changed it back to 07.00 AM starting on Feb.16 after the 10.00 AM execution expecting the job to run this morning and daily after that.

But no execution or job queuing was performed.

OK, I finally figured it out:

On Windows 10 (and perhaps earlier versions too) a power setting can cause the machine to shutdown instead of hibernating.

And that will cause FME server to shut down too.

This can be solved to switching to the "Maximum performance" power setting, which avoids the shutdown.

Sign up