Skip to main content
Best Answer

Limiting user job submissions in FME Flow

  • December 4, 2025
  • 4 replies
  • 47 views
maja
Contributor
Forum|alt.badge.img+8

I’m working with FME Flow 2025 and I’ve built a Flow App that allows users to run a workspace by clicking a “Run” button.

My concern is about system overload: if a user (maliciously or accidentally) clicks the “Run” button hundreds or thousands of times, this could flood the job queue and potentially saturate the single engine I have available.

I’ve looked into Job Queues and Job Routing Rules, but they only let me set priorities and routing conditions (repository). I understand that jobs can be routed to different engines using queues, but that’s not my goal. My goal is to limit the number of jobs submitted by users, not to distribute them across multiple engines.

What I’m trying to achieve is:

  • Prevent users from creating an infinite queue of jobs.

  • Ideally, enforce a limit per user (e.g., max 5 jobs active or queued).

Any ideas?

Best answer by hkingsbury

You could have a job that runs periodically (once or twice a minute?) that queries the queue, and drops any jobs when the user has exceeded the threshold.

Of course this would then require its own queue/engine to run so it doesn’t get blocked by the incoming requests!

4 replies

hkingsbury
Celebrity
Forum|alt.badge.img+67
  • hkingsburyCelebrity
  • Celebrity
  • Best Answer
  • December 4, 2025

You could have a job that runs periodically (once or twice a minute?) that queries the queue, and drops any jobs when the user has exceeded the threshold.

Of course this would then require its own queue/engine to run so it doesn’t get blocked by the incoming requests!

redgeographics
redgeographics
Celebrity
Forum|alt.badge.img+62

I agree with ​@hkingsbury here, and want to add that a CPU time engine would be ideal for those little maintenance jobs.

Ideally it would be an FME Flow setting though, I would suggest you create an idea for it so we can vote.

FME rocks! \m/
alexbiz
alexbiz
Influencer
Forum|alt.badge.img+31
  • alexbizInfluencer
  • Influencer
  • December 5, 2025

Hey everyone,
When creating a Schedule, there’s an option called “Skip if job in progress” that prevents a new job from being added if one is already queued or currently running. Maybe this kind of logic could be made available for Workspace Apps as well, and applied per user?

It seems like an interesting idea, although perhaps a bit high-level in terms of functionality. Still, it’s definitely worth submitting it to Safe as a feature request.

As far as I know, there’s currently no clean, built-in way to achieve this.

Draw it, map it, shape it, fix it, share it, change it, send, translate it 🎵
maja
Contributor
Forum|alt.badge.img+8
  • majaContributor
  • Author
  • Contributor
  • December 8, 2025

You could have a job that runs periodically (once or twice a minute?) that queries the queue, and drops any jobs when the user has exceeded the threshold.

Of course this would then require its own queue/engine to run so it doesn’t get blocked by the incoming requests!

Thank you for your responses.
I will write a script as suggested by ​@hkingsbury and submit this idea to Safe at the same time.

Community Stats

32,181
Posts
122,172
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.