Running a workspace on FME Flow creates a(n)...

Running a workspace on FME Flow creates a(n)...

• A. Automation
• B. Job
• C. Project
• D. Schedule

Answer: (B)

In FME Flow, executing a workspace creates a Job. A Job is a single execution instance of that workspace and carries its own status, timing, logs, and results. Each run you initiate—whether on demand or triggered by a schedule—spawns a new Job so you can track that specific execution independently. A project is the container that holds the assets like workspaces and settings, not the run itself. A schedule is merely a trigger that determines when a workspace should run; it defines when to run, not the execution record created by the run. So, the act of running a workspace on FME Flow is the creation of a Job.

In FME Flow, executing a workspace creates a Job. A Job is a single execution instance of that workspace and carries its own status, timing, logs, and results. Each run you initiate—whether on demand or triggered by a schedule—spawns a new Job so you can track that specific execution independently. A project is the container that holds the assets like workspaces and settings, not the run itself. A schedule is merely a trigger that determines when a workspace should run; it defines when to run, not the execution record created by the run. So, the act of running a workspace on FME Flow is the creation of a Job.