+3Hi,
I have observed when the workspace is executed through the FME Form, the log file is generated into the folder path mentioned under the Logging>Log File parameter.
However when the same workspace is published on FME flow and executed through the workspace app, it does not generate the log file in the folder path. The user can only download it through the FME flow under jobs
+28FME Flow job logs are designed to stay in their default location; moving them elsewhere would interfere with Flow’s job-management features.
To obtain a log file, users can:
download it directly from the FME Flow web interface
browse to the shared Resources\Logs directory on the server (or on the network if the system share was set up on a network drive)
retrieve it programmatically via the REST API (GET /jobs/{id}/log)
+60That is correct, and to be expected. Flow is a completely separate system from your Form installs. Like
+3Hi
Thank you for the response.
If I were to retrieve it using the REST API, do I need to make configurations to my workspace ?
+28No need to configure anything. Simply run your job on FME Flow and use its ID to request the log file through the API.
+60No need to configure anything. Simply run your job on FME Flow and use its ID to request the log file through the API.
Just an elaboration here: the logfile is being written during the workspace run, but not closed until the workspace is done, so you’ll need to request it afterwards, in a separate action.
+60One way, in an automation, would be to use an Email action to send an email with the log from the workspace as an attachment.
If you can tell us what you'd like to do with the log file, we can probably give you more detailed advice.
