Weaver: Workflow Execution Management Service (EMS); Application, Deployment and Execution Service (ADES); OGC API - Processes; WPS; CWL Application Package
created: datetime when the job was submitted and registered for upcoming execution
started: when a worker picked the job and started executing it
finished: when the job finished processing
We should add the following:
updated: last time the job was saved to database while the job is running
This would be a properly that always evaluates with utcnow() whenever saved in the database.
processed: last updated value during running status that indicates the processing was completed, but the job is not yet fully finished.
Once the job is done core execution computation (the actual processing: WPS, CWL, docker app, script, etc.),
processed gets set, but updated can still receive more updates after this (processing outputs, storing results, destroy docker instances, etc.).
Finally, finished gets set around the time when email notification is sent for final hand-off of the results location.
Final status = failed/succeeded is set and duration = finished - started is computed (already the case at the moment).
All jobs currently provide the following:
created
: datetime when the job was submitted and registered for upcoming executionstarted
: when a worker picked the job and started executing itfinished
: when the job finished processingWe should add the following:
updated
: last time the job was saved to database while the job is running This would be a properly that always evaluates withutcnow()
whenever saved in the database.processed
: lastupdated
value duringrunning
status that indicates the processing was completed, but the job is not yet fully finished.Once the job is done core execution computation (the actual processing: WPS, CWL, docker app, script, etc.),
processed
gets set, butupdated
can still receive more updates after this (processing outputs, storing results, destroy docker instances, etc.).Finally,
finished
gets set around the time when email notification is sent for final hand-off of the results location. Finalstatus = failed/succeeded
is set andduration = finished - started
is computed (already the case at the moment).Follow up on https://github.com/opengeospatial/ogcapi-processes/issues/184 for any update and alignment with specification if fields that more concrete definitions.
Refer to descriptions in PR: https://github.com/opengeospatial/ogcapi-processes/pull/185/files
Also, add the
/rec/core/job-status
inconformsTo
since above fields would all be supported.