I've no idea why it stops logging at that particular point, but in my experience it's a bad idea to log that many features to the FME log, it's not meant for that purpose.
If you need to look at the 428th item in a workflow I'd rather recommend the following pattern:
- Insert a Counter, make sure it starts counting at 1 and not 0
- After the Counter, insert a Tester and theck for _counter = 428
- Connect an Inspector to the Passed port
You may also want to look into the breakpoint functionality in FME, it's extremely handy in cases like these: https://desktopmanualbasic.safe.com/DesktopBasic3BestPractice/3.17.FeatureDebugging.html
The Workbench parameter 'max features to log' takes precedence over the Logger's parameter. It's in the Navigator under 'Workspace Parameters', and appears to be default set to 200, so not sure why yours is different. Anyway, you appear to be able to ramp it up as high as 999999999 if you want to open the taps and then use the loggers to reign that limit in.
The Workbench parameter 'max features to log' takes precedence over the Logger's parameter. It's in the Navigator under 'Workspace Parameters', and appears to be default set to 200, so not sure why yours is different. Anyway, you appear to be able to ramp it up as high as 999999999 if you want to open the taps and then use the loggers to reign that limit in.
Thanks, that did it. I was just trying to log why the translation is struggling with the few multipolygons in the dataset.