Execution from forms
After you create the integration object record, you can use the Execute form action to start the integration definition.
This action runs the triIntegration - Execute workflow. The integration object record becomes read only and its status changes to Processing. When the integration processing is completed with no errors, the integration object record changes back to the Ready state. If an error occurred during processing, the status changes to Failed, and the record does not change its state. You must then manually inspect the errors that occurred. However, you can override the inspection and change the record back to the Ready state by clicking the Complete action.
The Execute History section contains records with the details about each integration run. Each detail record contains the status, processing counts, and duration of the run. When an integration run has errors, it also includes a log of the errors and a query section that lists the individual records that failed. When the integration run is triggered from another workflow, the integration object record that contains the full overview of errors also contains a truncated message. The truncated message is in a hidden text field that can be displayed, for example, in an Attention message.
Outbound integrations can process a maximum of 1000 records at one time. If there are more than 1000 records to be exported, create your workflow logic to run the integration until all records are processed.