The Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues.

The input JSON paths In the DataRaptor Load must match the JSON from the OmniScript, otherwise the data will not be mapped correctly to the Salesforce fields. ContextId must be spelled correctly in the merge code that passes the Recordld to the DataRaptor, otherwise the DataRaptor will not be able to identify which record to update. The fields that are not updated are not necessarily read only in Salesforce, as they could be editable by other means. In the DataRaptor Load, in the Preview tab, the Record is from the wrong record type has no effect on updating data in Salesforce, as it is only used for testing purposes.

The correct syntax for passing all of the parent FlexCard's records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.

An Integration Procedure Action can execute an Integration Procedure that contains multiple elements, such as DataRaptor Actions, HTTP Actions, or other Integration Procedure Actions. This can be used to save data to multiple systems, such as Salesforce and AWS Order Management, in one OmniScript element.

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:
* A. "The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript." This is a common configuration issue. If the paths between the OmniScript's structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.
* B. "The fields that are not updated are read-only in Salesforce."If a field is Read-Only at the field- level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.
Incorrect Options:
* C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.
* D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.
:
Salesforce OmniStudio Developer Guide # DataRaptor Load # Troubleshooting Salesforce Help Documentation: OmniStudio DataRaptor Best Practices