pub struct SyncJobRunSchema {Show 17 fields
pub id: Option<String>,
pub args: Option<Map<String, Value>>,
pub resources: Option<Vec<SyncJobResourceSchema>>,
pub sync_job_id: Option<String>,
pub integrated_account_id: Option<String>,
pub status: Option<SyncJobRunSchemaStatus>,
pub daemon_id: Option<String>,
pub daemon_group_key: Option<String>,
pub webhook_id: Option<String>,
pub error_handling: Option<SyncJobRunSchemaErrorHandling>,
pub ignore_previous_run: Option<bool>,
pub version: Option<i64>,
pub resource_stats: Option<SyncJobRunResourceStats>,
pub created_at: Option<String>,
pub updated_at: Option<String>,
pub started_at: Option<String>,
pub finished_at: Option<String>,
}Fields§
§id: Option<String>The ID of the sync job run.
args: Option<Map<String, Value>>The arguments passed to the sync job run.
resources: Option<Vec<SyncJobResourceSchema>>§sync_job_id: Option<String>The ID of the sync job that this sync job run belongs to.
integrated_account_id: Option<String>The ID of the integrated account that this sync job run belongs to.
status: Option<SyncJobRunSchemaStatus>The status of the sync job run. created - waiting to run, running - running, rate_limited - temporarily paused after an upstream rate-limit response and will resume automatically after backoff, completed - completed successfully, failed - failed, stopped - stopped by the user.
daemon_id: Option<String>The daemon_id attribute of a daemon that is running this sync job.
daemon_group_key: Option<String>The name of the daemon group that this sync job run should be assigned to. Used while creating a sync job run. Truto find a daemon in the group that is available to run the sync job. You can either specify daemon_group_key (Daemon) or webhook_id (RapidBridge), but NOT both while creating a Sync Job Run.
webhook_id: Option<String>The ID of the webhook where the sync job records need to be sent. You can either specify daemon_group_key (Daemon) or webhook_id (RapidBridge), but NOT both while creating a Sync Job Run.
error_handling: Option<SyncJobRunSchemaErrorHandling>Specifies the error handling strategy used for the sync job run. fail_fast - stop the sync job run as soon as an error is encountered, ignore - continue running the sync job run even if an error is encountered. In case of ignore, you’ll receive sync_job_run:record_error events for each error encountered. In case of batch, you’ll receive sync_job_run:record_error events with multiple errors batched into the errors array, this is only supported when the version used for Sync Job Run is 2.
ignore_previous_run: Option<bool>Specifies if the sync job run was started ignoring the previous run date.
version: Option<i64>The runtime version of the sync job run. The version 1 is the default version and the version 2 is the new version which supports batch error handling and other enhancements.
resource_stats: Option<SyncJobRunResourceStats>The statistics of the resources synced in the sync job run. This will have information around how many records were fetched and persisted by the sync job run – grouped by the resource and method. The data is updated every 10 seconds while the sync job run is running.
created_at: Option<String>The date and time when the sync job run was created.
updated_at: Option<String>The date and time when the sync job run was last updated.
started_at: Option<String>The date and time when the sync job run was started.
finished_at: Option<String>The date and time when the sync job run was finished.