Skip to main content
Question

Failed Feature Types (warnings) vs Failed Reader (errors) ... does Form need additional parameters

  • January 22, 2026
  • 2 replies
  • 30 views

j.botterill
Influencer
Forum|alt.badge.img+56

The failed feature type issue

We are reading in many featureclasses using GEODATABASE_SDE reader in workspace and recently noticed an issue in FME Form (24.1) where it only throws a warning

“A table name ‘HeritageSites_Exclusion’ could not be found in the geodatabase as either a featureclass or table. This may be due because the current user does not have permissions to see HeritageSites_Exclusion”

The rejected feature handling is set to Terminate

The workspace runs in success, although this missing table was joined upon and is necessary for the right outcome. 

I guess I’m posting here to see if others have/had this issue, where only a warning of a missing featuretype is given… we believe it should be an Error

 

Workaround

Obviously, we can place NoFeatureTesters and connect a Terminator to the NoInput port. This is alot of work, so we looked into parameters

Unsure how the Reader parameter “Ignore Failed Readers” truly works. It seems designed very early on to Error if the dataset/database fails to connect. Fine for single datasets, but perhaps unwhelming for workspaces with dataset/databases with many FeatureType. In this issue/case, only one featuretype is missing from the geodatabase, so a warning is thrown. Warnings are often missed in comparison to error and termination.

Changing Ignore Failed Readers to Yes doesn’t capture missing FeatureTypes

As pictured, running this parameter as Yes or No, still resulted in the warning and no features coming out of the missing featuretype

2 replies

ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • January 22, 2026

Something similar ArcSDE FeatureReader - Workspace succeeds even when there is an error | Community

 

I suspect this may be an issue relating to ArcSDE readers only, and the Ignore Failed Readers works as you would expect with other readers.

 

In your scenario using a FeatureReader, do you get the warning in the log file but nothing out the rejected port?


s.jager
Influencer
Forum|alt.badge.img+23
  • Influencer
  • January 22, 2026

In general I’m sometimes a bit baffled by when a workspace runs “succesfully”, but still has not written anything to the database for example. I do not see much logic to when a reader or writer will fail or when it will just log a warning and continue. I recently ran into an issue where I needed to Delete some rows from a join-table. These rows were read from that same table, without any geometry, and the writer was set to Delete. The workspace still Failed due to no geometry, when all it really needed was the primary key… Any of the other attributes are not needed/necessary in this case.

I do think there is a need for additional reader/writer configuration options, like failing or not failing on warnings, rolling back to the state before the workspace was run, disabling certain types of warnings, etc.