Skip to main content
Open

FME Flow recursion detection

Related products:FME Flow
  • February 20, 2025
  • 5 replies
  • 92 views

redgeographics
Celebrity
Forum|alt.badge.img+62

In our standard FME Flow training course we have one excercise where Workspace A does some checks on user parameters and if they are succesful it runs Workspace B through an FMEFlowJobSubmitter.

One of our trainees accidentally set up the FMEFlowJobSubmitter to run Workspace A instead and when he published it to Flow he made a recursive loop: every time Workspace A ran, it queued Workspace A again. I was busy helping somebody else at that time so when I got around to his question I noticed it had ran 17000+ jobs in a matter of minutes. These were low-impact jobs, so it wasn’t an immediate problem, but it’s safe to say that this has the potential of completely overwhelming an FME Flow setup.

After talking to Safe we decided to post it as an idea here to see if others have come across this as well or have opinions about it.

The big question would be:

Should FME be able to detect these recursion risks?

And in a broader sense: have you had this happen to you? Or something similar that you think FME should be able to detect and warn you about?

 

5 replies

redgeographics
Celebrity
Forum|alt.badge.img+62
  • Author
  • Celebrity
  • February 20, 2025

I recall one similar thing happening at a training course many years ago where a trainee had set up a schedule with a short interval (something like 5 seconds) to run 3 workspaces that each took 10 seconds to run. This was right before lunch and after lunch he was wondering why his machine was so sluggish. There were hundreds, if not thousands, of jobs in the queue.


ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • February 20, 2025

The classic one for me is using a workspace runner without the child workspace having feature inspectors turned off. Only an immediate impact on me, frantically trying to close the pop up windows so I could go to the workspace to kill the parent job.


redgeographics
Celebrity
Forum|alt.badge.img+62
  • Author
  • Celebrity
  • February 20, 2025

The classic one for me is using a workspace runner without the child workspace having feature inspectors turned off. Only an immediate impact on me, frantically trying to close the pop up windows so I could go to the workspace to kill the parent job.

I think I’ve had that happen to me at least once too 😅


liamfez
Influencer
Forum|alt.badge.img+44
  • Influencer
  • February 20, 2025

I have also had that happen before with the inspectors.

I have not had this recursive loop happen to me yet thankfully. However I would agree that it would be a beneficial feature, maybe as a setting that is default on but could be turned off. Perhaps under the Advanced Run options for workspaces.


LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • April 29, 2025
NewOpen