Disadvantage of triggering events inside a workspace using a transformer rather than in an Automation?

• A. The workspace can trigger an event during a translation, rather than at the end of it.
• B. You won't know whether the workspace completed successfully or not when the event is triggered.
• C. The workspace does not need to be run on FME Server to take this action. It will produce the same result when run using FME Desktop.
• D. The workspace will always be slower when using FME Desktop instead of FME Server.

Answer: (B)

Triggering events inside a workspace with a transformer fires while the translation is still running, so you don’t have a reliable indication of the final outcome. The workspace hasn’t finished yet, and the Automation can only know the run’s status after completion. That means you can’t depend on that event to know whether the workspace ultimately succeeded or failed, which is why this approach is a disadvantage. In contrast, handling the event in an Automation lets you act on the definitive result of the run (success or failure) and respond appropriately. The other statements don’t address this reliability issue about final status, so they don’t capture the core drawback of triggering inside the workspace.