Failed to read features using the 'STADIA' reader when writer esri gdb

Hi ​@charry ,

Thanks for your post! This is definitely something worth investigating.

To help us troubleshoot, could you provide a bit more information?

• What version of FME Form are you using? (Help > About FME)
• What operating system are you on?
• Approximately how many features are you expecting the STADIA reader to return?
• Does the failure happen at the same point each time, or is it random?
• Can you share a snippet from your FME translation log showing the error message?
• If possible, could you share a simplified version of your workspace and a small sample of data to help us reproduce the issue?

The combination of STADIA reader + Esri geodatabase writer is a specific workflow, so capturing the exact failure point will help us identify whether this is a data issue or something with the reader in FME.

If this is urgent for your work, I'd recommend opening a support ticket at https://support.safe.com/s/submit-case so our team can work with you directly.

Hi ​@charry 

We had the same error message until today and it also occurred with other writers. We’re using version 2025.2.4. The message appears when the preset basemap "Stadia" is used in the map view of the data preview.
After disabling it, the annoying message is gone.
@Safe: However, it’s more than just an annoying message, because after every refresh of the map view in the data preview, the message appeared again and switched to the translation log.
It also wasn’t possible to keep the data preview and translation log views separated permanently.

Kind regards

Bernd

Same issue here with the Stadia backgrounds in the visual preview.  I got around it by standing up an OSM mirror in Docker and using that, but there is definitely something amiss in Version 2025.

Thank you all for sharing these details! It does sound quite disruptive, especially the constant switch to the log.

I've not been able to reproduce this exact error with the default Stadia basemap on my end. Does switching to a different basemap in the Data Preview suppress the issue? 

Also, do you happen to have a custom Stadia basemap configured under Utilites> FME Options > Background Maps? I've seen similar error spam when custom WMTS basemaps have configuration issues, so it would be great to rule that out.

If you're willing to share a log file with debug enabled (Utilities > FME Options > Translation > Log Debug ) and/or a sample workspace, that would be really helpful!