Completed

SelectJobs>Completed.

Finished jobs appear in the Completed table. By default, jobs older than four weeks are removed from the table. To change the length of time completed jobs appear, adjust theJob Historyscheduled cleanup task.

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

Note  "> NoteSome fields do not display by default. To control which columns display, click the Customize Columns icon.
Tip  "> TipYou can filter the list of jobs based on the values of some columns. To set filters, expand theFiltersdrop-down.
  • Id: The unique ID of the completed job.
  • Workspace: Theworkspacerequest that was run.
  • Repository: The repository containing theworkspacethat was run.
  • Username: TheFME Flowuser that ran the job. When a job is run directly through theFME Flowweb services, this value matches the value ofRan By. When a job runs in the context of theseFME Flowmechanisms,Usernamemeans 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 Appsand AR Apps (no authentication required): The user that owns the security token that is used to run the job from the app.
    • Workspace Appsand AR 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.
    • RunWorkspacewith FMEFlowJobSubmitter transformer: The user account that authenticates theFME Flowconnection in the transformer.
  • Ran By: TheFME Flowuser that ran a job. When a job is run directly through theFME Flowweb services, this value matches the value ofUsername. When a job runs in the context of theseFME Flowmechanisms,Ran Bymeans 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 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.
    • RunWorkspacewith FMEFlowJobSubmitter transformer: The user account that authenticates theFME Flowconnection in the transformer.
  • Status: The status of the finished job. To learn more click on the job to examine its properties and log file.
  • Logs: Indicates if any errors or warnings were logged when the job ran. Click the icon to view thejob log、过滤错误和/或警告。
  • Started: The date and time when the job was started.
  • Finished: The date and time when the job was finished.
  • Source Name: Identifier of theFME Flowmechanism from which the job originated, such as an Automations ID or Schedule Category name.
  • Source Type:FME Flowmechanism from which the job originated, such asAutomationsorSchedules.Source TypeFME Flowmeans the job originated from aremote engine.
  • Queue Type: The type of queue in which the job ran:
    • System: The queue is configured to run jobs on the nativeFME Flow.
    • Remote: The queue is configured to route jobs to aremote engine.
      • Note  "> NoteJobs that run onRemotequeues appear asSystemwhen viewed on the remoteFME Flowon which the job ran.
  • Engine: The name of the FME engine that processed the job and theFME Flowhost on which the engine was running.
  • Queue: Thequeuein which the job ran.
  • % CPU: The percentage of total processing time that is recorded as CPU time, calculated asCPU Time/Elapsed Time.
  • CPU Time: Total CPU time to run the job, as recorded by theFME FlowREST API.
    • Note  "> NoteThe REST API record ofCPU Timediffers fromFME FlowandFME Formlogs because it includes additional start and end scripting, and is a more accurate report of total processing time.
  • Elapsed Time: Total processing time of the job, calculated asFinished-Started.
  • Peak Memory Usage: The peak memory used by the FME Engine while processing a job, minus the memory in use by the FME Engine at the beginning of the job.
    • Note  "> NoteDue to differences betweenFME FormandFME Flowin how FME Engines restart between translations,FME Formdoes not subtract the memory in use by the FME Engine at the beginning of the job when reportingPeak Memory Usage, but simply records peak memory at any time during the translation. With this additional calculation,FME Flowprovides a more accurate report ofPeak Memory Usage, and in particular, a more accurate value when reportingAverage Peak Memory Usageforworkspacemetrics.