I do this using a FMEServerJobSubmitter or with a HttpCaller to the API. Schedule the single workspace that submits the children. Does that work for you?

In addition to what @nielsgerrits has already suggested you could also chain them together in one big automation and run that on a schedule.

Hi @gfaulkner,

I agree with nielsgerrits the easiest way to do this since you have so many workspaces to schedule would be to create a parent workspace to submit all of these. I'd take a look at the FME Server Rest API and first I'd make a call to list all the workspaces in that repository:

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/repositories/items_get_5

Then you can flatten the response JSON to retrieve the workspace name as an attribute which can be used in a second HTTPCaller in the Request URL to submit the jobs, rather than this being something you have to set manually for each one.

https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations/submit_post_29

There is also an existing idea requesting a Schedule for Repositories so please consider adding a vote and any supporting comments here: https://knowledge.safe.com/content/idea/77546/scheduling-a-repository-to-run-workspaces-as-a-bat.html

@hollyatsafe @nielsgerrits @redgeographics

Hi All. thanks for your responses. I'll up vote the existing idea. We ended up using 4 parent workspaces with FMEServerJobSubmitter's to meet our needs.

Thanks again, Grant