Skip to main content
Question

Tracking down WorkSpace started FME workspaces

  • November 12, 2025
  • 6 replies
  • 56 views

lambertus
Enthusiast
Forum|alt.badge.img+23

Hi guys,

This week I created a nice model A with runs smoothly combined with a main script B which includes a workspacerunner triggering workspace A. Is there a way I can track whether all the scripts started by the Workspace Runner are ready?

In my case 21 features entered the WorkspaceRunner, starting model A, which leads to creation of 18 Excel files which is perfect. I would like to create a log somehow that 21 workspaces were started and 21 workspaces were completed resulting in 18 Excel files in this case.

Workspace B now states that the WorkspaceRunner is finished, however, on the background workspace(s) A is still running for some time.

 

6 replies

nielsgerrits
VIP
Forum|alt.badge.img+61

I do not know of a native way. When I need this I let the parent workspace fill a postgres table with a record for each feature and the child workspace update this record when finished.

Setting it up this way has the advantage of being able to pause or abort the processing and not having to process all previously processed data again.

But it will take some work and I only use this when I need to process a lot of data, which is not very often.


lambertus
Enthusiast
Forum|alt.badge.img+23
  • Author
  • Enthusiast
  • November 12, 2025

I do not know of a native way. When I need this I let the parent workspace fill a postgres table with a record for each feature and the child workspace update this record when finished.

Nice idea! Will dive into that one.


ebygomm
Influencer
Forum|alt.badge.img+45
  • Influencer
  • November 12, 2025

Do you just need to be notified when all child workspaces are complete or continue further processing?


hkingsbury
Celebrity
Forum|alt.badge.img+64
  • Celebrity
  • November 12, 2025

Is it not just a case of setting “Wait for Job to Complete” to “Yes”?

 

 


ebygomm
Influencer
Forum|alt.badge.img+45
  • Influencer
  • November 13, 2025

Is it not just a case of setting “Wait for Job to Complete” to “Yes”?

 

 

It’s not an option if you want child jobs to run concurrently. 


lambertus
Enthusiast
Forum|alt.badge.img+23
  • Author
  • Enthusiast
  • November 14, 2025

Is it not just a case of setting “Wait for Job to Complete” to “Yes”?

 

 

It’s not an option if you want child jobs to run concurrently. 


Both Yes or No for this setting are not completely satisfactory. Because in both cases the Child workspace or workspaces might be running while the Parent Workspace is ready. There is a kind of black box idea, because there is no other log which states whether all started Child workspaces are finished. Adding a FeatureWriter with a log file at the end of Child workspace is an interesting idea for like ​@nielsgerrits  suggested.