Why is my logger not logging

I’ve encountered a lot of strange behavior when publishing or republishing to FME Flow, where it sometimes looked like the connections between transformers were missing. It’s quite difficult to reproduce though.

Could you try republishing your workspace under a different name and/or to a different repository and test again?

I’m pretty sure that there is/was something going on with FME Form while publishing the workspace. We could try to look for diffs between your local workspace file and the one that has been published.

I’ve just run a similar workspace and it runs successfully but no mention of the AttributeManager so I don’t think that’s significant

025-08-22 11:39:25|   0.1|  0.1|INFORM|Creating writer for format: 
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Creating reader for format: 
2025-08-22 11:39:25|   0.1|  0.0|INFORM|MULTI_READER(MULTI_READER): Will fail with first member reader failure
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Using Multi Reader with keyword `MULTI_READER' to read multiple datasets
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Using MultiWriter with keyword `PRIMARY_DEST' to output data (ID_ATTRIBUTE is `multi_writer_id')
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Writer output will be ordered by value of multi_writer_id
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Loaded module 'Geometry_func' from file 'D:\FMEServer\Server\fme\plugins/Geometry_func.dll'
2025-08-22 11:39:25|   0.1|  0.0|INFORM|FME API version of module 'Geometry_func' matches current internal version (4.0 20240212)
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Emptying factory pipeline
2025-08-22 11:39:25|   0.1|  0.0|INFORM|Logger: Feature is:
2025-08-22 11:39:25|   0.1|  0.0|INFORM|+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Even if I set the Creator to Number to Create 0 so nothing ever hits the logger I still get a reference to the logger in the log file

Logger_Logger (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)

In the end I swapped out the AttributeManager for a ParameterFetcher that seemed to do the trick. Still no idea why. 

I’d be interested what happens if there were another transformer - even just a Junction - between Logger and Writer. 

Also, if the Logger worked if you connected it separately. So AttributeManager > Logger is one connection and AttributeManager > Writer is another. 

It’s ok if you don’t. You probably have better things to do. I’m just curious. When I have weirdness like this, it’s often somehow due to what’s connected after the transformer in question.

Yeah, I played around already with a few different things. That was also my assumption too. I know that FME somehow does some look ahead and can process things out of order. My assumption is that something funny like that was going on. 

Another reason why I prefer the individual transformers (especially the ParameterFetcher) over the AttributeManager!

I’ve had a similar issue in the past (process overall worked so didn’t really investigate further). Were any changes made to the logger parameters or just the default?

I think I set the number of feature to log to be lower that the standard but I can’t remember.