Skip to main content
Solved

2025.1.3.2 b25646 creating ".sentry-fme" folder in workspace directory

  • November 4, 2025
  • 4 replies
  • 138 views

a-a-ron
Contributor
Forum|alt.badge.img+2

Hi,

I recently upgraded from 2025.1.1.0 b25615 to 2025.1.3.2 b25646 and noticed that whenever I open a .fmw file, a new folder, “.sentry-fme” is created in the same directory.

When I started FME from my desktop shortcut, a “.sentry-fme” folder was created on my desktop once the program was up and running.

Could we get this fixed? I’d rather not bloat my directories with temporary files if I can help it. I’ve since downgraded back to 2025.1.1.0.

Thanks,

Best answer by jeroenpeters

@a-a-ron ​@jeroenpeters ​@philippeb I’m just confirming that the fix is in the latest 2025.1 release and also the 2025.2 beta.

I can confirm this. We've deployed FME 2025.1.3.3 (b25648) and this problem is solved. 

4 replies

jeroenpeters
Contributor
Forum|alt.badge.img+5
  • Contributor
  • November 5, 2025

I have the same issue and contacted the support team about it. They confirmed it's a bug that will be fixed in a future version. It may already be resolved in the current beta.

 

Thank you for contacting Safe Software and bringing this to our attention for this version of FME Form. This is a bug, there have been a few customers that have run into it and we have recently implemented a fix. Would you be able to try out our beta version and see if this addresses the issue? 


philippeb
Enthusiast
Forum|alt.badge.img+22
  • Enthusiast
  • November 6, 2025

This is super annoying. I have folders everywhere now !

The entire team upgraded to the latest version...


DanAtSafe
Safer
Forum|alt.badge.img+21
  • Safer
  • November 6, 2025

@a-a-ron ​@jeroenpeters ​@philippeb I’m just confirming that the fix is in the latest 2025.1 release and also the 2025.2 beta.


jeroenpeters
Contributor
Forum|alt.badge.img+5
  • Contributor
  • Best Answer
  • November 7, 2025

@a-a-ron ​@jeroenpeters ​@philippeb I’m just confirming that the fix is in the latest 2025.1 release and also the 2025.2 beta.

I can confirm this. We've deployed FME 2025.1.3.3 (b25648) and this problem is solved.