Skip to main content
Question

FME Flow REST API (via Data Virtualization) Asynchronous Job Status Values - Complete vs Success

  • September 2, 2026
  • 3 replies
  • 53 views

chriswilson
Enthusiast
Forum|alt.badge.img+29

I was checking through the list of possible job status for an asynchronous (Data Virtualization) workflow I have going and didn’t find a definition for ‘complete’, or a comparison of that value to ‘success’.  I was referring to the REST API V4 documentation here: https://support.safe.com/hc/en-us/articles/38420159907213-Submitting-a-Job-through-the-FME-Flow-REST-API-V4

 

Would someone with familiarity around those statuses be able to clarify the meaning of ‘complete’ and how it contrasts to ‘success.  AI relented from guessing and admitted it didn’t know.

 

An update to this is that ‘complete’ is not listed in the OpenAPI spec for the FME Flow REST API V4, so at this stage is the documentation incorrect?

https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json

          "status": {
"type": "string",
"description": "The current status of this job",
"enum": [
"queued",
"running",
"success",
"failure",
"cancelled"
]
},
          

3 replies

todd_davis
Influencer
Forum|alt.badge.img+23
  • Influencer
  • September 2, 2026

Looks like a mistake in the article that they include “complete” as an option. We certainly don’t have any in any of our job statuses.


chriswilson
Enthusiast
Forum|alt.badge.img+29
  • Author
  • Enthusiast
  • September 2, 2026

I agree Todd, but I though it best to confirm so that others can also see it/documentation can be updated.


chriswilson
Enthusiast
Forum|alt.badge.img+29
  • Author
  • Enthusiast
  • September 3, 2026

@zoe.forbes can we confirm that complete is not a valid job status?