The “View Log” option in the Automations has recenly started pointing towards the entire automations logs folder rather than the logging of that specific Automation? This is less than helpful when debugging so I would like to suggest it be brought back.
I’m noticing this in FME Flow 2023.2.1 (and my colleague doesn’t have it in an older build)
+17We found the work around to use Start Debug on the automation instead of regular start automation.
Start Debug will send you directly to Log automation. But have that option back for regular start automation would be nice!
+14Hey,
We really really need the old automation logs to see what’s going on in the automations.
Now it is very hard to find what’s been logged for a specific automation.
Are there any known drawbacks to run automations in debug mode?
(Besides the facts it is not recommended and truly doesn’t feel right...)
Please, bring the old type of Automation logs back asap!
Thanks
+6Are there any known drawbacks to run automations in debug mode?
(Besides the facts it is not recommended and truly doesn’t feel right...)
I agree about it feeling wrong to run a production automation in debug mode. But having all of the logged messages for a given automation in chronological order and in one place is necessary for me, so I guess that’s what I’ll do.
+33Has anyone discovered any useful way to actually find the errors that are reported on the automations screen?
+15Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
