|A convenience ID to track jobs. While generally unique, idempotency is NOT enforced.
|The hotglue environment ID
|The flow ID, found in the General or Settings tab of your flow
|An optional identifier passed when triggering jobs via API. Job names are auto-assigned when triggered by webhooks or the scheduler.
|The tenant ID, usually 1:1 with your internal ID for your customer
|Usually the same as the tenant ID
|A unique path identifying the job. The S3 root is ALWAYS unique for a given job
|The UTC datetime at which the task began running
|An optional JSON object that holds webhook payloads, API write job payloads, and other data for use in targets and ETL scripts
|The data source of the job.
|The data target of the job
|In V2 flows, the connector linked by the user. This may function as a source or a target
|In V2 flows, whether the job is of type
|The lifecycle status of the job
|A boolean value, denoting whether or not the job was kicked off by hotglue's scheduler.
|Jobs that run with a
state.json are denoted as
incremental_sync. All other jobs will be a
|An optional datetime passed to the job that overrides the start_date and state.json. This date is not persisted outside of a given job
|The error or success message from a given job. For failing jobs, this will be hotglue's best prediction of the cause of the failure, although it may not always provide full context.
|This is an internal hotglue ID used for debugging.
|Denotes whether the job runs on hotglue's
|An object with metrics defining the memory, CPU, and server location that a job runs on
|The last registered job event, in UTC. For completed jobs, this will be the time of completion.
recordCount shows the number of records fetched for each stream
exportSummary is displayed when using a target built on hotglue's SDK. This shows each stream that was written to a hotglue target, with the number of records in each state: success, fail, existing, updated
exportDetails shows a more detailed view of the export summary. This will include the
id of the created record in the external system, and, if passed, the
externalId that you send with each record.
|An object containing the error message
|The size of job files, in megabytes
|The amount of memory and CPU used. This can offer clues if your ETL script has memory leaks or inefficiencies
Updated about 2 months ago