The bulk operation was rolled back because one of the records wasn’t processed successfully. See AllOrNoneHeader.
You can’t submit a record that is already in an approval process. You must wait for the previous approval process to complete before resubmitting a request with this record.
You must designate an assignee for the approval request (ProcessInstanceStep or ProcessInstanceWorkitem).
The changes you are trying to make can’t be completed because changes to the associated master-detail relationships can’t be made.
Your client applicationblind carbon-copied an email address on an email even though the organization’s Compliance BCC Email option is enabled. This option specifies a particular email address that automatically receives a copy of all outgoing email. When this option is enabled, you can’t BCC any other email address. To disable the option, log into the user interface and from Setup, click Security Controls | Compliance BCC Email.
Your client application blind carbon copied the logged-in user’s email address on an email even though the organization’s BCC COMPLIANCE option is set to true. This option specifies a particular email address that automatically receives a copy of all outgoing email. When this option is enabled, you can’t BCC any other email address. To disable the option, log into the user interface and from Setup, click Security Controls | Compliance BCC Email.
An update to a product caused by a cascade can’t be done because the associated product is active.
You can’t change the type of a field that is referenced in an Apex script.
You can only create one managed package in an organization.
You can’t deactivate Divisions if an assignment rule references divisions or if the DefaultDivision field on a user record isn’t set to null.
You must have at least one DatedConversionRate record if dated conversions are enabled.
You can’t modify components that are included in a managed package.
You must have at least one active administrator user.
If you exceed the limit of five IP ranges specified in a profile, you can’t enable restriction of login by IP addresses. Reduce the number of specified ranges in the profile and try the request again.
You do not have permission to create, update, or activate the specified record.
You can’t modify components that are included in a managed package.
You can’t rename a field that is referenced in an Apex script.
You can’t rename an object that is referenced in an Apex script.
You can’t define a new parent record for the specified record.
A sendEmail() call could not resolve an object name.
A converted lead could not be updated.
You can’t disable the corporate currency for an organization. To disable a currency that is set as the corporate currency, first use the user interface to change the corporate currency to a different currency, and then disable the original currency.
You can’t change the corporate currency for an organization from the API. Use the user interface to change the corporate currency.
You can’t change the owner of or define sharing rules for a record that is a child of another record if you do not also have the appropriate permissions on the parent. For example, you can’t change the owner of a contact record if you can’t edit its parent account record.
You can’t create a circular dependency between metadata objects in your organization. For example, public group A can’t include public group B, if public group B already includes public group A.
You do not have permission to access the community that this entity belongs to. You must be given permission to access the community before you can access this entity.
You can’t exceed the maximum size for a CLOB field.
You have reached the maximum number of custom objects or custom fields for your organization.
You have reached the maximum number of indexes on a field for your organization.
You can create only one custom index per field.
You have reached the maximum number of custom links for your organization.
Your organization has reached its custom metadata maximum limit.
Your organization has reached its custom settings maximum limit.
You have reached the maximum number of custom tabs for your organization.
You can’t delete a record because it is in use by another object.
You can’t perform the requested operation because of an existing dependency on the specified object or field.
You can’t create a relationship between the specified case and solution because it already exists.
Custom object or custom field IDs must be unique.
You can’t create a custom object or custom field with a duplicate master name.
You can’t create a custom object or custom field with a duplicate developer name.
A user-specified external ID matches more than one record during an upsert.
You can’t create a custom object or custom field with a duplicate master name.
A sendEmail() call could not choose between OrgWideEmailAddress.DisplayName or senderDisplayName. Define only one of the two fields.
A create, update, or upsert failed because of a duplicate user name.
You can’t supply a duplicate value for a field that must be unique. For example, you may have submitted two copies of the same session ID in a invalidateSessions() call.
Because of an error earlier in the call, the current email was not processed.
The Scontrol file name was empty, but the binary was not empty.
You can’t update a record if the date inLastModifiedDate is later than the current date.
You can’t access a record if it has been archived.
You can’t reference an object that has been deleted. Note that this status code only occurs in version 10.0 of the API and later. Previous releases of the API use INVALID_ID_FIELD for this error.
You can’t edit a record that is locked by an approval process.
You can’t add an organization to more than one Environment Hub.
An email address is invalid, or another error occurred during an email-related transaction.
The activation of a Contract failed.
You can’t define a custom validation formula that violates a field integrity rule.
You can’t violate field integrity rules.
The creation of the lookup filter failed because it exceeds the maximum number of lookup filters allowed per object.
Your attempt to upload an HTML file failed. HTML attachments and documents, including HTML attachments to a Solution, can’t be uploaded if the Disallow HTML documents and attachments checkbox is selected under Setup, in Security Controls | HTML Documents and Attachments Settings.
The image exceeds the maximum width, height, and file size.
The owner of the specified item is an inactive user. To reference this item, either reactivate the owner or reassign ownership to another active user.
An operation affects an object that is cross-referenced by the specified object, but the logged-in user does not have sufficient permissions on the cross-referenced object. For example, if the logged-in user attempts to modify an account record, that user might not have permission to approve, reject, or reassign a ProcessInstanceWorkitem that is submitted after that action.
You can’t perform the specified action because you do not have sufficient permissions.
You can’t define a new sharing rule if it provides less access than the specified organization-wide default.
You supplied an argument that is of the wrong type for the operation being attempted.
You specified an assignee type that is not a valid integer between one and six.
You specified an assignment rule that is invalid or that is not defined in the organization.
The specified batch operation is invalid.
The outgoing email has anEmailFileAttachment with an invalidcontentType property. See RFC2045 – Internet Message Format.
The specified credit card information is not valid.
The specified value in a relationship field is not valid, or data is not of the expected type.
The specified cross reference type is not valid for the specified field.
You must specify a positive, non-zero value for the currency conversion rate.
You can’t modify the corporate currency conversion rate.
The specified currency ISO code is not valid..
A specified email address is invalid.
You can’t set the value for owner to null.
Invalid parameters were specified when subscribing to an event.
You specified an invalid field name when trying to update or upsert a record.
You can’t combine a person account record type change with any other field update.
You can’t use an email template with an invalid field name.
The specified filter action can’t be used with the specified object. For example, an alert is not a valid filter action for a Task.
The specified ID field (ID, ownerId), or cross-reference field is invalid.
A specified Inet address is not valid.
You can’t clone a Pricebook2 or PricebookEntry record if those objects are not active.
The solution is invalid. For example, this error can occur if you try to associate a translated solution with a master solution when another translated solution in the same language is already associated with the master solution.
The outgoing email’s References or In-Reply-To fields are invalid. These fields must contain valid Message-IDs. See RFC2822 – Internet Message Format.
There is no applicable approval process for the specified object.
The specified operator is not applicable for the field type when used as a workflow filter.
You specified an invalid or null value for a restricted picklist.
The specified partner network status is invalid for the specified template field.
You can’t delete a person account.
You can’t create, update, or delete data while the instance where your organization resides is being upgraded to the latest release. Please try again after the release has completed. For release schedules, see trust.salesforce.com.
You must specify true or false for the saveAsActivity flag.
The specified sessionId is malformed (incorrect length or format) or has expired. Log in again to start a new session.
The specified organization status change is not valid.
The specified type is not valid for the specified object.
The specified type is not valid for the specified operation.
The specified value is not valid for the specified field’s type.
The specified IP address is outside the IP range specified for the organization.
The number of records you attempted to purchase from Data.com exceeds your available record addition limit.
You have exceeded the number of licenses assigned to your organization.
You attempted an action with a high-volume portal user that’s not allowed. For example, trying to add the user to a case team.
You have exceeded a limit. The limit may be on a field size or value, license, or other component.
An email containing a security token was sent to the user’s email address because he or she logged in from an IP address that is not included in their organization’s list of trusted IP addresses. The user can’t log in until he or she adds the security token to the end of his or her password.
The user logged in from an IP address that is not included in their organization’s list of trusted IP addresses, but a security token has not yet been issued.
The user must add a security token to the end of his or her password to log in.
An ID must be either 15 characters, or 18 characters with a valid case-insensitive extension. There is also an exception code of the same name.
A manager has not been defined for the specified approval process.
A mass mail retry failed because your organization has exceeded its mass mail retry limit.
The organization has exceeded its daily limit for mass email. Mass email messages can’t be sent again until the next day.
You have exceeded the maximum number of specified CC addresses in a workflow email alert.
You have exceeded the document size limit for a dashboard.
You have reached the maximum number of levels in a hierarchy.
You have exceeded the maximum size of an attachment.
You have exceeded the maximum size of a document.
You have exceeded the maximum number of actions per rule.
You have exceeded the maximum number of active rules.
You have exceeded the maximum number of approval steps for an approval process.
You have exceeded the maximum number of formulas per rule.
You have exceeded the maximum number of rules for an object.
You have exceeded the maximum number of entries for a rule.
The task description is too long.
You have exceeded the maximum number of rules per Territory.
You have exceeded the maximum number of rule criteria per rule for a Territory.
A merge operation failed.
You did not specify a required argument.
You can’t insert a reduction order item if the original order shipping address is different from the shipping address of other items in the reduction order.
A process() request failed because the record submitted does not satisfy the entry criteria of any active approval processes for which the user has permission.
Your organization does not permit email attachments.
You can’t add members to an inactive Division.
You do not have permission to send the specified email. You must have “Mass Email” if you are sending mass mail or “Send Email” if you are sending individual email.
The number specified is outside the valid range of values.
The number of history fields specified for the sObject exceeds the allowed limit.
The operation you attempted can’t be performed for one or more users. For example, you can’t add high-volume portal users to a group.
An email can’t be sent because the specified User has opted out of mass mail.
The logged-in user can’t access an object that is in a licensed package if the logged-in user does not have a license for the package.
A create User operation failed because you can’t create a second portal user under a Contact.
You can’t have a private contact on an asset.
You can’t access a record if it is currently in use by a workflow or approval process.
A request that has been running too long may be canceled.
A call requires a field that was not specified.
You can’t recursively update or delete the same object from an Apex trigger. This error often occurs when:
You try to update or delete an object from within its before trigger.
You try to delete an object from within its after trigger.
This error occurs with both direct and indirect operations. The following is an example of an indirect operation:
A request is submitted to update Object A.
A before update trigger on object A creates an object B.
Object A is updated.
An after insert trigger on object B queries object A and updates it. This is an indirect update of object A because of the before trigger of object A, so an error is generated.
You can’t delete a sharing rule for a parent record if its child record needs it.
(API version 18.0 and higher) The organization has exceeded its daily limit for single emails. Single email messages can’t be sent again until the next day.
Custom prices can’t be defined without corresponding standard prices.
You have exceeded your organization’s storage limit.
The specified string exceeds the maximum allowed length.
You have exceeded the number of tabs allowed for a tabset.
The template specified is unavailable. Specify another template or make the template available for use.
An operation can’t be performed because a territory realignment is in progress.
The specified text uses a character set that is not supported.
Too many Apex requests have been sent. This error is transient. Resend your request after a short wait.
A request failed because too many values were passed in for a multi-select picklist. You can select a maximum of 100 values for a multi-select picklist.
You can’t assign the record to the specified User because the user does not have read permission.
A deadlock or timeout condition has been detected:
Deadlocks involve at least two transactions that are attempting to update overlapping sets of objects. Note that if the transaction involves a summary field, the parent objects are locked, making these transactions especially prone to deadlocks. To debug, check your code for deadlocks and correct. Deadlocks are usually not the result of an issue with Salesforce operations.
Timeouts occur when a transaction takes too long to complete, for example, when replacing a value in a picklist, or changing a custom field definition. These are temporary states. There is no corrective action needed.
If an object in a batch can’t be locked, the entire batch fails with this error.
The appropriate default record type could not be found.
An object could not be undeleted because it does not exist or has not been deleted.
The system encountered an internal error. Please report this problem to Salesforce.