Sign in

v1

latestOpenAPI 3.0.3Apache 2.02026-07-17302459.9 KB
Data Jobs Execution

Get Data Job Execution details.

<i>(Introduced in v1.0)</i>

get/data-jobs/for-team/{team_name}/jobs/{job_name}/executions/{execution_id}

Response

Execution details

idstring

Data Job Execution ID

job_namestring

Data Job name

status'submitted' | 'running' | 'succeeded' | 'cancelled' | 'skipped' | 'user_error' | 'platform_error'

The current status

type'manual' | 'scheduled'

Execution type - manual or scheduled

start_timestring date-time

Start of execution

end_timestring date-time

Start of execution

started_bystring

User or service that started the execution (e.g manual/auserov@example.mail.com or scheduled/runtime)

logs_urlstring

URL link to persisted logs in central location. Logs generally should be available for longer time. The link is available only if operators have configured it during installation of Control Service. During install operators can configure logs to be persisted to log aggregator service whose link can be exposed here.

messagestring

Message (usually error) during execution

op_idstring

Operation id used for tracing calls between different services

Example response

{
  "id": "starshot-processing-vmc-fact-daily-2018623174356",
  "job_name": "starshot-processing-vmc-fact-daily",
  "status": "submitted",
  "type": "scheduled",
  "started_by": "schedule/runtime",
  "logs_url": "http://logs/jobs?filter=job-name",
  "deployment": {
    "job_version": "11a403ba",
    "python_version": "3.9",
    "mode": "release",
    "id": "release",
    "deployed_by": "auserov@example.mail.com",
    "schedule": {
      "schedule_cron": "0 0 13 * 5"
    },
    "resources": {
      "cpu_request": 10,
      "cpu_limit": 20,
      "memory_request": 1024,
      "memory_limit": 2048
    }
  }
}