This article will walk you through how to troubleshoot Ironclad integration errors.

This article covers the most common integration errors seen in Ironclad. If you run into an issue that is not mentioned here or are having difficulties implementing the suggested fixes, reach out to Ironclad Support.

Skip To:

• Salesforce Integration Errors
  • Resolve a Real-Time Sync Errors
  • Resolve a Record Sync Error
  • Common Record Sync Error Messages
• Coupa Integration Errors
  • Workflow Sync Errors

Salesforce Integration Errors

If you want to learn more about Salesforce integration errors, refer to the Salesforce FAQ .

Resolve a Real-Time Sync Error

1. Click your name located in the top right corner of Ironclad. Click Company Settings > Errors.
2. Filter the Entity Type by Workflow. The entity ID is based on the “Entity Type”. If the entity type is a “workflow”, then the ID describes a specific workflow accessible from the dashboard. If the entity type is a “workflow template”, then the ID references a workflow template accessible in workflow designer.
3. Filter the Integration by Salesforce.
4. If you want to filter by a specific date range, select a start date and end date.
5. Each error message describes what went wrong. If you are unable to resolve the issue, reach out to Ironclad Support and copy the Error ID.

Resolve a Record Sync Error

Required Role: Administrator
If an error displays on the Record Sync Errors page, Ironclad has already tried to resolve it by attempting to retry syncing multiple times. The error then requires manual action to resolve or dismiss the error.

Some error messages can be ignored. For example, if you examine the Ironclad Repository record (the hyperlinked workflow ID) and the associated record in Salesforce to verify that the data is correct in both systems, click Ignore to dismiss the error. The specific error message for this Ironclad record is removed from the page. If you ignore a record, it does not impact other records.

1. Click your name located in the top right corner of Ironclad. Click Company Settings > Integrations.
2. Click on the Salesforce integration, and then click the Record Sync Errors tab. All of the errors that have occurred while trying to sync Ironclad’s Repository records to Salesforce display. Errors are listed in reverse chronological order, with the latest errors at top.
3. Based on the error information, try and resolve the error. After you attempt to resolve it, click Resync above the error. Ironclad tries to sync that specific record to Salesforce again. It will not impact other records of the same record type. If the record successfully syncs, Ironclad removes the error listing including the retry records.
4. If a new error occurs for the same workflow, a new error for the workflow displays with a different error description.

Common Record Sync Error Messages

The table below details some commonly encountered record sync errors and solutions. If you run into an issue that is not mentioned here, or are having difficulties implementing the suggested fixes, reach out to Ironclad Support.

Error Message	Potential Meaning	How to Fix
java.lang.IllegalStateException: Unable to sync objects for the following mappings:	This is likely an error on Ironclad’s side. There is an issue with syncing a record to the Salesforce account for certain mappings.	Check which mapping(s) are having issues by looking at the body of the error message. Find the record’s record type by clicking on the Record ID in the Record Sync Errors tab of the Salesforce configuration page in Ironclad. You are taken to the Repository with the record’s details. Identify the record’s records type in the Record Type column. Click the Record Sync tab. Go to the record sync configuration for the record type that is associated with the record. Look for the field, or fields, flagged for having errors to determine the root cause. Attempt to resolve the error, and then in the Record Sync Errors tab, click Resync. Example In this example, CustomerSignedId is the Salesforce field with a problem. The field is used in the Counterparty Signed By Ironclad field, so take a look at the mapping. There are a couple of potential problems: The error message could mention a possible issue with the Salesforce sub-field FirstName. The First Name sub-field is improperly mapped to the Counterparty Phone field. Correct this by mapping First Name to the correct name field. The Ironclad record could be missing a value for Counterparty Phone Number. You can fix this by updating the Repository record to add the missing data. Click on the link from Record Sync Errors tab (hyperlinked Workflow ID) to be taken directly to the repository page. Click Add Property and add a value for the missing field.
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY with message: record type missing for: Contact	This is likely an error on Salesforce’ side. There was an issue with creating the Salesforce object.	First, check that the Salesforce Service Account (linked at the Ironclad company level, not personal user level) has create permissions in Salesforce or that Salesforce object (e.g. the Contact).  If that does not resolve the issue: the Salesforce object may have required field(s) that need to be set in order to create that object, but the Ironclad mapping is missing those fields. — One solution would be to add in the missing mappings to Ironclad under the ‘Record Sync’ tab. — Alternatively, you could change the object’s settings in Salesforce to make this field optional. Click Resync to retry the sync.

Coupa Integration Errors

Workflow Sync Errors

1. Click your name located in the top right corner of Ironclad. Click Company Settings > Errors. Errors are listed in reverse chronological order, with the latest errors at top.
2. Filter the Entity Type by Workflow. The entity ID is based on the “Entity Type”. If the entity type is a “workflow”, then the ID describes a specific workflow accessible from the dashboard. If the entity type is a “workflow template”, then the ID references a workflow template accessible in workflow designer.
3. Filter the Integration by Coupa.
4. If you want to filter by a specific date range, select a start date and end date.
5. Each error message describes what went wrong. If you are unable to resolve the issue, reach out to Ironclad Support and copy the Error ID.