Coming soon!The skip_destination_events job setting skips destination events for a job run. This setting is useful for migrations into an empty destination platform where all destination events are known on the initial job run and are not needed for a delta job run. Therefore, this setting would be enabled after the initial job run since additional destination events would not be needed. The setting turns off the destination events for the next delta job run only, and then the setting resets. Therefore, if you want to disable destination events for additional delta job runs, you will need to patch the job again before each job run. Disabling the destination events can lessens rate limits and, therefore, migration delays for large migration projects.
This setting is available through the REST API only. You will use the following PATCH call to update the job to enable the skip_destination_events setting.
| Code Block |
|---|
PATCH {{url}}v1/jobs/{{job}}?reset=skip_destination_events |