FME Flow: 2024.2

Running

Select Jobs > Running.

The following columns are available to display in the Running table:

Note  Some fields do not display by default. To control which columns display, click the Customize Columns icon.
Tip  You can filter the list of jobs based on the values of some columns. To set filters, expand the Filters drop-down.
  • Id: The unique ID of the running job.
  • Workspace: The workspace request that was run.
  • Repository: The repository containing the workspace that was run.
  • Username: The FME Flow user that ran the job. When a job is run directly through the FME Flow web services, this value matches the value of Ran By. When a job runs in the context of these FME Flow mechanisms, Username means the following:
    • Automations: The user that last enabled the automation to run the job.
    • Schedules: The user that last updated the schedule.
    • Streams: The user who owns the stream.
    • Workspace Apps (no authentication required): The user that owns the security token that is used to run the job from the app.
    • Workspace Apps (authentication required): The user that owns the security token that is used to run the job from the app.
    • Automation Apps: The user that owns the security token that is used to run the job from the app.
    • Webhook URL: The user that owns the security token for the webhook URL.
    • Run Workspace with FMEFlowJobSubmitter transformer: The user account that authenticates the FME Flow connection in the transformer.
  • Ran By: The FME Flow user that ran a job. When a job is run directly through the FME Flow web services, this value matches the value of Username. When a job runs in the context of these FME Flow mechanisms, Ran By means the following:
    • Automations: The user that manually triggers an automation with a Manual Trigger or an FME Flow Schedule trigger, which runs the job. Otherwise, the user that last started the automation that ran the job.
    • Schedules: If the job triggered automatically according to schedule settings, the user that last updated the schedule. If that user no longer exists, the current owner of the schedule. Otherwise, the user that manually triggered a schedule to run the job.
    • Streams: The user who started the stream.
    • Workspace Apps (no authentication required): The user that owns the security token that is used to run the job from the app.
    • Workspace Apps (authentication required): The user that authenticated to run the job through the app.
    • Automation Apps: The user that authenticated to run the job from the app.
    • Webhook URL: The user that owns the security token for the webhook URL.
    • Run Workspace with FMEFlowJobSubmitter transformer: The user account that authenticates the FME Flow connection in the transformer.
  • Status: The current status of the job.
  • Started: The date and time when the job was started.
  • Source Name: Identifier of the FME  Server mechanism from which the job originated, such as an Automations ID or Schedule Category name. If the source is a mechanism that was removed after the job was submitted (such as an automation, automation app, schedule, or stream), this field indicates that it is a Deleted mechanism.
  • Source Type: FME Flow mechanism from which the job originated, such as Automations or Schedules. Source Type FME Flow means the job originated from a remote engine.
  • Queue Type: The type of queue in which the job was run:
    • System: The queue is configured to run jobs on the native FME Flow.
    • Remote: The queue is configured to route jobs to a remote engine.
      • Note   Jobs that run on Remote queues appear as System when viewed on the remote FME Flow on which the job ran.
  • Engine: The name of the FME Engine processing the job and the FME Flow host on which the Engine is running.
  • Queue: The queue in which the job was run.