I was hoping someone who understands how FeatureHolder works can let me know if I can use it successfully to help with an issue I am having.

I have some workspaces on flow that had been working as expected for well over a year but recently I have had two separate ones glitch on me in the span of a few weeks.

I am not 100% sure what went wrong but from looking at the log, the portal feature service reader did not read in all of the records from the table. Looking through the log, I see a line that indicates the metadata fme is accessing lists the correct number of records in the table. However, the summary shows that for that run, it actually read in less than that number.

I have not yet identified what caused the reader to behave this way in these two instances.

My question is:

If I put a feature holder right after the reader, will that solve this problem? Will it make the workspace wait until all of the records are read in? (i.e. the number read in matches the number it was given by the feature service metadata)