Run into an action error? We've got you. Below you'll find a list of known action errors with explanations and next steps.
First, enter the error into the search in our support library, if it's a documented and known error, it will lead you right back here for further instruction and save you from scrolling through the list. If a search for the error in the support library does not return any information, it's something we haven't come across yet, contact support and we'll help you through it!
Pro tip: Clicking on "Contact Support" in the left navigation of the Intelligence360 Platform doesn't only offer the option to start a chat, you can also search our articles in the "Find your answer now" section. You can search your error there without ever leaving the Platform.
Errors can be a result of a simple misconfiguration, incorrect permissions, CRM issues, interrupted integrations, etc. The type of error will dictate the "Next Steps" in the table below in one of three ways:
-
User Resolvable: If an error is resolvable by you, the user, we'll provide you with instructions to do so. Note: Some user resolutions may require an admin, but can still be accomplished without support.
-
Engage i360 Support: If an error requires Intelligence360 intervention or hasn't yet been discovered and documented, we'll direct you to contact our awesome support team.
-
Outside Contact: Some errors are the result of an outside issue, like a rule set in a CRM, in which case we will recommend who you should contact, like a Salesforce Admin.
User Resolvable
Error |
What's Happening? |
Next Steps |
Malformed id. Assigned To ID: id value of incorrect type: [...] |
Field configuration doesn’t match the type field for that field in Salesforce. |
Check the trigger configuration of the specified action for the incorrect value that is writing to ID field. |
Team or user integration is not enabled for user: fix-user-integration |
An integration has failed. |
Follow this guide: How do I reconnect my failed integration? |
Salesforce Error*** Use one of these records? |
A Salesforce duplicate has appeared. |
Snooze the action repeatedly, once the Salesforce duplicate is recognized by the Platform, the error will resolve itself. |
Invalid field for insert update. Duration and EndDateTime must match. |
Both a start and end date and duration were added and the duration doesn’t match the calculation of start to end. |
Drop duration from the configuration. |
No default value given for auto-run action schema items { "firstName": "", "lastName": "" } |
Tried to run an action where first and last name fields were empty, fields were not pre-populated. |
"firstName" and "lastName" are String properties so you will pre-populate First Name and Last Name fields using this guide: Pre-populate String |
Cannot insert update activate entity. n2de.DETaskTrigger: execution of AfterInsert\ ***INSUFFICIENT_ACCESS_OR_READONLY |
The person assigned doesn't have access to do anything to the linked object. |
|
"\"Insufficient access on cross reference entity. insufficient access rights on cross-reference id: 0011O00002Ld2fn\"", |
Person assigned to the action doesn't have access to do anything to the linked object. |
|
http request failed |
The external system is overwhelmed or having general problems. |
Please try again in a few minutes. If auto-run action, it should clear up automatically. |
"\"Promise timed out after 120000 milliseconds\"", |
The external system is overwhelmed or having general problems so we aren’t getting a response back. Sometimes the write succeeds but the external system doesn’t let us know. |
Please try again in a few minutes. If auto-run action, it should clear up automatically. |
"\"Bad Request - Please check content type mappings: task.\"" |
The action tried to write to a field that is read-only or no longer available to write to. |
Check action configuration and make sure that all fields that are being written to are available to do such. |
"\"Entity is deleted. entity is deleted\"" |
The content you are trying to update has been deleted in the external system. |
Once we sync and mark the content as been deleted, the auto ran actions should dismiss by themselves. Feel free to dismiss the action before this point though. |
"\"Only absolute URLs are supported\ |
This happens when the user running the action isn’t properly authenticated. |
Delete/Reconnect the user integration that is failing. |
"\"read ECONNRESET\"" |
Timeout from the external server. |
Auto-run actions should self fix. Manual actions, complete the action again. |
"\"Internal_Error\"" |
The external server is having problems. |
Auto-run action should retry and auto-resolve. Manual actions should just be retried after a few minutes. |
"\"Duplicates detected. Use one of these records?\"" |
We tried to create a record that already exists. |
Auto-run actions should auto-dismiss. Snooze manual actions. |
"\"Invalid or null for restricted picklist. Task Type: bad value for restricted picklist field: Email\"" |
This error occurs when the picklist field referenced in the error messaged meetings each of these conditions. |
Remove the default value from the Record Type or picklist field. |
"\""\"Unable to create/update fields: XXXXX, XXXX. Please check the security settings of this field and verify that it is read/write for your profile or permission set."" |
User does not have permissions to read/write to the Salesforce object. |
Have an admin give the permissions needed to read/write in Salesforce. Have the admin check the field level security for a profile from Setup->Administration setup->Profiles. |
"error": "\"[strict_dynamic_mapping_exception] mapping set to strict, dynamic introduction of [somefieldname] within [content.account] is not allowed\"", |
Trying to write to a platform field that currently doesn’t exist. This is sometimes caused by a timing issue where actions try to write to a field before it's been property created. |
Auto-run actions should auto-resolve after some time. Manual actions should be retried in a few minutes. |
"error": "\"authorizationUrl\"" |
An internal error that means the customer has not completed the connection flow for the integration. |
|
"\""\"Unable to create/update fields: XXXXX, XXXX. Please check the security settings of this field and verify that it is read/write for your profile or permission set."" |
User does not have permissions to read/write to the Salesforce object. |
Have your Salesforce admin give the permissions needed to read/write in Salesforce. Check the field level security for a profile from setup>administration setup>profiles. |
"error": "\"Sales Engineer: id value of incorrect type: somefieldvalue\"" |
User is trying to write a non-ID to an ID field. Eg., a name for Sales Engineer instead of the ID for that name. |
Change what to write to the field as the appropriate ID. |
Request Timeout after 60000ms |
The external system is overwhelmed or having general problems so we aren’t getting a response back. Sometimes the write succeeds but the external system doesn’t let us know before the given timeout. |
Please try again in a few minutes. If auto-run action, it should clear up automatically. |
Engage i360 Support
Error |
What's Happening? |
Next Steps |
Salesforce Error*** Use one of these records? |
|
|
Salesforce Error***n2de.DETaskTrigger: execution of AfterInsert |
|
|
Invalid or null for restricted picklist. bad value for restricted picklist field: Name |
|
|
No auto-run eventTrigger found {"typeRun": true, "configEnabled": false, "hasAutoRunEventTrigger": true} |
|
Outside Contact
Error |
What's Happening? |
Next Steps |
Task Record Type ID: this ID value isn't valid for the user: [...] |
Assignee doesn't have correct permissions for task record type. |
Contact your Salesforce Admin to adjust user permissions to access task record type. |
You are not permitted to edit a Closed Opportunity. Please contact SalesOps for assistance. |
The action was run against a closed opportunity where Salesforce has a rule against, or the assignee doesn’t have access to edit closed opportunities |
Check with your Salesforce Admin. |
Specific additional info referred to in links in the tables above:
Error conditions for "\"Invalid or null for restricted picklist. Task Type: bad value for restricted picklist field: Email\":
-
The referenced picklist field has 'Restrict picklist to the values defined in the value set' set to Enabled.
-
The referenced picklist field is a dependent picklist.
-
The page layout does not include both the controlling and dependent picklist fields.
-
A default value is set for the referenced picklist field:
-
If the object includes Record Types - This error occurs if the record type sets the default value.
-
If the object does not include Record Types - This error occurs if the picklist field sets the value.
-
All record types should have the newly create picklist selected in the Selected items section and not under available items.
-
-
Initiate a Mass Quick Action with Predefined Value Set
-
Any active trigger on the object where the field is used can give the same error.
When you attempt to save a record in the Object that contains this picklist field, Salesforce attempts to populate the default value. Since the controlling value is not set and the picklist is restricted to only allow the dependent values, you will receive this error when you attempt to save the record.
Additional Causes:
-
This error can occur when you deploy a picklist field from sandbox and the values are not selected on the record types.
-
This error can occur when the value 'Label' and 'API Name' are different in the values, and you use the 'Label' name in the update.
Comments
0 comments
Please sign in to leave a comment.