Skip to main content
Archived

Auto-Pause After Inactivity for FME Flow Hosted Instances

Related products:FME Flow Hosted
maddiel
siennaatsafe
danilo_fme
davideagle
+9
  • gerhardatsafe
  • maddiel
    maddiel
  • siennaatsafe
    siennaatsafe
  • danilo_fme
    danilo_fme
  • davideagle
    davideagle
  • carlm
    carlm
  • crutledge
    crutledge
  • neilhellas
  • sigher
    sigher
  • mikeyrobins
  • mark2atsafe
    mark2atsafe
  • NickAtSafe
    NickAtSafe
  • dalimelki
    dalimelki
  • jlebrun24
    jlebrun24

dalimelki
Contributor

In FME Flow Hosted, forgetting to manually pause an instance after use can lead to unnecessary cloud costs. While it's currently possible to create a daily scheduled pause, this method can be frustrating — for example, if you're actively working on the instance at the scheduled pause time, the instance will shut down anyway, interrupting your work and requiring a restart.

1. Auto-Pause Based on Inactivity

Introduce an option when creating (or editing) an FME Flow Hosted instance to auto-pause after a user-defined period of inactivity, such as 30 or 60 minutes.

  • Inactivity could be defined as: no jobs running, no automations triggered, and no user interaction in the Web UI or API.

  • The timeout should be configurable by the user.

Benefit: This eliminates the need to rely solely on fixed scheduled pauses and helps avoid instances being left running unnecessarily — especially overnight or during weekends.

 

Why This Matters:

  • Prevents wasted cloud spend due to forgotten instances.

  • Reduces frustration caused by hard-scheduled pauses that stop active work.

  • Encourages smarter and more sustainable resource usage.

4 replies

NickAtSafe
Safer
Forum|alt.badge.img+4
  • Safer
  • May 10, 2025

Hi ​@dalimelki!

Thanks for reaching out. Your question about auto-shutdown after a period of time is a popular question from our users. We’d love to implement something like this internally, but we’re unable to do so.

FME Flow Hosted’s security model is setup in such a way that not even the development team who built/maintain Flow Hosted have access to the actual FME Flow instance on the machines we maintain - we have no way of knowing what is happening on those instances, like when jobs were last run. 

Now, that said, I do have an option that you may want to try out. I’ve whipped up a workspace that will check your Flow instance for activity and let you pause it.

Pre-requisites:

  • FME Flow Hosted API Token - this can be created from your dashboard. Login to Flow Hosted → click on your account name on the top right corner → Settings → API Tokens.
  • The Instance Id of the instance that you want to control from Flow Hosted
  • FME Flow Web Service/Connection setup in FME Form (details here) - this is what you’d use in Form to connect to your Flow instance

Using the attached workspace (which I hope is documented enough for you to adjust if you need), upload it to your Flow instance and schedule it to run on a regular basis (every 10 minutes? every hour?). It’ll check the job history of your flow instance, ignoring this job (based on the filename), and check how long ago your last job was completed. If it exceeds your threshold time, it’ll send the command to the Flow Hosted API to shut down your instance. 

Note: the attached workflow was built in 2025.0, so I’ve included screenshots below if you need to replicate it in a older version.
 

Parameters


 

Part 1
Part 2

I hope this helps - please don’t hesitate to reach out with any further questions or new ideas!


NickAtSafe
Safer
Forum|alt.badge.img+4
  • Safer
  • May 10, 2025
NewArchived

NickAtSafe
Safer
Forum|alt.badge.img+4
  • Safer
  • May 10, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

dalimelki
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • May 12, 2025

Many Thanks ​@NickAtSafe !

 

That was helpful , I’ll definitely share it internally and reach out to you if I have any questions.

 

Regrards,


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings