| Function Call | Error Text | Resolution |
|---|---|---|
| Add | Invalid value specified for function parameter. Function Name: ADD Parameter Name: Value Parameter Ordinal: 2 Parameter Type: Numeric Submitted Value: | A NULL or empty value was passed to the second parameter in the Add function call. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| AttachFile | The EMAIL_ATTACHMENTS business rule must be turned on before using the AttachFile function | The AttachFile AMPscript function is related to the Email Attachments documentation. If you have not had this feature enabled for your account, contact your Account Executive to enable. |
| AttachFile | FileReference parameter cannot be null or an empty string | The AttachFile function has two required parameters. If either have a null or empty string the function call fails. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| BarCodeURL | The barcode value cannot be null or empty string | The submitted value to the BarCodeURL function is null or empty. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
Base64Decode | Invalid length for a Base-64 char array or string. | The value being decoded is not a valid Base64 format. Specifically, the number of characters is smaller or larger than expected. Ensure that the data has not been inadvertently truncated. |
Base64Decode | The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. | This can occur if a character is added to the end of a Base64 string. Ensure the value being decoded is in valid Base64 format. |
BuildRowSetFromXML | Invalid xml found in xml parameter | Ensure the XML being passed to the function call can be parsed. Tip: Use an editor that recognizes different languages to help detect any issues with the XML format. |
| ClaimRow | The required Data Extension name for a ClaimRow function call is empty. | Ensure the first parameter has a value for a valid Data Extension name. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| ClaimRow | The Data Extension name for a ClaimRow function call is invalid. | Ensure the Data Extension exists with the exact name in the function call. Ensure it is wrapped in quotes. If using a shared data extension, check permissions to the Data Extension for the business unit making the function call. |
| ClaimRowValue | A ClaimRowValue function call did not find a row to claim in the target data extension and no default value was supplied. | There were either no rows available or all rows were claimed. |
| CloudPagesURL | Page not found. Either PageID is invalid or does not belong to BU. | Ensure the PageID passed in the first parameter is a numeric value and can be found in the Business Unit from which the CloudPagesURL function is being called. |
| Concat | Cannot CONCAT more than 500000 characters | The number of characters being concatenated exceeds the maximum limit of 500000. |
| ContentAreaByName | Content Area "my contents\2022_test_content" could not be found. | Confirm the content lives in the folder path provided in the function call. If the content or folder names do not match exactly, this call will fail. |
| ContentBlockbyId | Invalid value specified for function parameter. | A null or empty value was passed for the ID parameter. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| ContentBlockbyId | The specified content block does not exist | The ID value does not exist. Ensure the correct number was passed. |
| ContentBlockbyId | Failed to convert parameter value from a String to a Int32 | Check out Email fails with the error Failed to convert parameter value from a String to a Int32 |
| ContentBlockbyKey | The specified content block does not exist | The key value does not exist. Ensure the key matches exactly. Check the difference between the content block name and key, as these do not always match. |
| ContentBlockbyName | Could not resolve content path. | Confirm the content lives in the folder path provided in the function call. If the content or folder names do not match exactly, this call will fail. |
| ContentImagebyID | The specified image does not exist | The ID passed either does not exist or exists but the Content type is not an Image. |
| ContentImagebyID | Invalid value specified for the function parameter | A null or empty value was used for the ID. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
ContentImagebyKey | The specified image does not exist | The Key passed either does not exist or exists but the Content type is not an Image. |
CreateSalesforceObject | Call to create the salesforceobject Lead failed! Error status code: DUPLICATES_DETECTED | This error can happen for Leads, Contacts, or Accounts when attempting to create a duplicate record. Review the Manage Duplicate Records documentation for more details on this feature. |
| CreateSalesforceObject | Call to create the salesforceobject CampaignMember failed! Error status code: CANNOT_UPDATE_CONVERTED_LEAD | The LeadId passed to the CreateSalesforceObject function call to create a CampaignMember was converted to a Contact. Updates cannot happen on converted leads. Use the new ContactID instead. |
| CreateSalesforceObject | Call to create the salesforceobject {Object} failed! Error status code: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY Error message: insufficient access rights on cross-reference id: 0031A00001abcde | Ensure the Salesforce System User has access to both the object being created and the reference id, in this case the Contact being used. |
| DateAdd | Invalid value specified for function parameter. Function Name: DateAdd Parameter Name: InputDate Parameter Ordinal: 1 Parameter Type: Date Submitted Value: | A null or empty value was used for the InputDate parameter. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| DateAdd | Invalid value specified for function parameter. Function Name: dateadd Parameter Name: Number Parameter Ordinal: 2 Parameter Type: Numeric Submitted Value: | A null or empty value was used for the dateadd parameter. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| DateDiff | Invalid value specified for function parameter. Function Name: DateDiff Parameter Name: BeginDate Parameter Ordinal: 1 Parameter Type: Date Submitted Value: | A null or empty value was used for the BeginDate parameter. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| DateDiff | Invalid value specified for function parameter. Function Name: DateDiff Parameter Name: EndDate Parameter Ordinal: 2 Parameter Type: Date Submitted Value: | A null or empty value was used for the EndDate parameter. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| DateParse | String was not recognized as a valid DateTime | Ensure the date format follows our documentation. Confirm the Accounts Settings | Date Format matches the format of the date value passed to the DateParse function. For example, if my Date Format is "English (United States)" but the date value I pass is '31/01/2022 12:00 PM' the function will error. For more information, review our Developer Documentation on Date and Time Formats . |
| DateParse | The date string to be parsed cannot be null or an empty string | A null or empty value was passed. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| DatePart | Invalid value specified for function parameter. Function Name: DatePart Parameter Name: Date Parameter Ordinal: 1 Parameter Type: Date Submitted Value: 24.01.2021 | The date used in the DatePart function is not a valid format. Review our document on on Date and Time Formats. |
| DatePart | Invalid value specified for function parameter. Function Name: Datepart Parameter Name: Date Parameter Ordinal: 1 Parameter Type: Date Submitted Value: | A null or empty value was passed. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Divide | Invalid value specified for function parameter. Function Name: divide Parameter Name: Value1 Parameter Ordinal: 1 Parameter Type: Numeric Submitted Value: | A null or empty value was passed. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Field | Invalid column name (parameter 2) passed to Field function. No column of the specified name was found. Invalid Field Name: Birthday Function: Field( @Customer, "Birthday" ) | When building the rowset from which the Field function is referencing, ensure the field names match. In this particular case, the Data Extension has a field called "DOB" but not "Birthday". |
| Field | Invalid row (parameter 1) passed to Field function. Row is null or empty. Function: FIELD(@Customer, "DOB") | The variable @Customer has no data. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Field | Invalid index (parameter 2) passed to Field function. Index is null or empty. Function: Field(@Customer, AttributeValue("Address")) | The attribute value for "address" for the record returned no data for the subscriber. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Format | Invalid value specified for function parameter. Function Name: Format Parameter Name: DataType Parameter Ordinal: 3 Parameter Type: Text Submitted Value: date1 | The third parameter in the Field function only has two valid values, "Date" or "Number". In this case, the value passed was "date1" which is invalid. |
| FormatCurrency | The input value (undefined) cannot be formatted as a number. The first parameter value for a FormatNumber call must be a numeric type supported by the requested format. Value: undefined Format: C | The submitted value was the text string "undefined" which is not a number. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| FormatCurrency | An error occurred when attempting to retrieve the culture's numeric format for a FormatCurrency function call. The passed culture value may not be valid. The third parameter value for a FormatNumber call must be a recognized culture name such as en-US, en-GB, es-ES, fr-FR, de-DE, or ja-JP. See inner exception for detail. Culture: en_TW | The culture code value of en_TW is invalid. Reference our Supported Number, Name, and Address Formats (ICU). |
| FormatDate | An error occurred when attempting to retrieve the culture's date time format for a FormatDate function call. The passed culture value may not be valid. The fourth parameter value for a FormatDate call must be a recognized culture name such as en-US, en-GB, es-ES, fr-FR, de-DE, or ja-JP. See inner exception for detail. Culture: en_FR | The culture code value of en_FR is invalid. Reference our Supported Number, Name, and Address Formats (ICU). |
| FormatNumber | The input value () cannot be formatted as a number. The first parameter value for a FormatNumber call must be a numeric type supported by the requested format. Value: Format: N2 | There was a null or empty value passed to the FormatNumber function. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| FormatNumber | An error occurred when attempting to retrieve the culture's numeric format for a FormatNumber function call. The passed culture value may not be valid. The third parameter value for a FormatNumber call must be a recognized culture name such as en-US, en-GB, es-ES, fr-FR, de-DE, or ja-JP. See inner exception for detail. Culture: R$ | The culture code value of R$ is invalid. Reference our Supported Number, Name, and Address Formats (ICU). |
| FormatNumber | An error occurred when attempting to evaluate a FormatNumber function call. The specified D format cannot be applied to decimal values (0.0). It is only valid for integer types. The first parameter value for a FormatNumber call must be a numeric type supported by the requested format. Value: 0.0 Format: D3 | The second parameter in the FormatNumber function dictates the format of the resulting number. In this particular case, you cannot go from Decimal to Decimal. Instead, try the Fixed Point (F3). E.g. %%=FormatNumber("0.0","F3","en-US")=%% would result in 0.000. |
| GetPortfolioItem | Could not find URL for Portfolio item. Member ID: 1234567 Customer Key: Footer_text | The GetPortfolioItem function references the legacy Portfolio feature. Ensure the content exists in the Portfolio folder. If this feature does not exist, it is not possible to enable. Instead, use the ContentBlock AMPscript functions, such as ContentBlockByKey. |
| HTTPGet | The remote server returned an error: (403) Forbidden. | Ensure that you have the correct permission to retrieve content from this URL. Reach out to the owner of the URL for further assistance if needed. |
| HTTPGet | The remote server returned an error: (404) Not Found | Check the URL for accuracy. Ensure the URL has not been modified or moved. |
| HTTPGet | The remote server returned an error: (429) Too Many Requests. | The owner of the URL has limits in place to the number of requests allowed to the URL. This can be too many requests at one time, or too many requests over a period of time. Work with the owner of the URL to better understand what limits are in place so that your calls do not fail. Alternately, look into storing the content directly within a Content Block within Marketing Cloud. Storing content locally typically results in quicker email send speeds than emails making HTTPGet calls to retrieve content. |
| HTTPGet | The remote server returned an error: (500) Internal Server Error | Contact the URL owner to understand if there are any issues with their service |
| HTTPGet | The remote name could not be resolved: 'yourURLdomain.com' | Contact the URL owner to understand if there are any issues with their service |
| HTTPGet | The URL parameter is empty. A valid URL must be included for the HTTPGet function call. | Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| HTTPPost | The remote server returned an error: (400) Bad Request | The server has responded that this is a malformed request. Ensure the content being posted to the URL is syntactically correct. Ensure any required header values are also passed. |
| HTTPPost | The remote server returned an error: (403) Forbidden. | Ensure that you have the correct permission to post content from this URL. Reach out to the owner of the URL for further assistance if needed. |
| HTTPPost | The remote server returned an error: (404) Not Found | Check the URL for accuracy. Ensure the URL has not been modified or moved. |
| HTTPPost | The remote server returned an error: (429) Too Many Requests. | The owner of the URL has limits in place to the number of requests allowed to the URL. This can be too many requests at one time, or too many requests over a period of time. Work with the owner of the URL to better understand what limits are in place so that your calls do not fail. |
| HTTPPost | The remote server returned an error: (500) Internal Server Error | Contact the URL owner to understand if there are any issues with their service |
| HTTPPost | The remote server returned an error: (502) Bad Gateway. | Contact the URL owner to understand if there are any issues with their service |
| HTTPPost | The remote server returned an error: (504) Gateway Timeout. | Contact the URL owner to understand if there are any issues with their service |
| HTTPPost | The remote name could not be resolved: 'yourURLdomain.com' | Contact the URL owner to understand if there are any issues with their service |
| InsertDE | The Data Extension name for a InsertDE function call is invalid. A Data Extension of this name does not exist. Data Extension Name: SendLog | Ensure the data extension name matches what is being used in the InsertDE function. Tip: Consider using the productized Send Logging feature instead of AMPscript. |
| Lookup | The Lookup function call failed because the specified lookup field does not exists for the data extension Data Extension: Products Invalid Field Name: ProductNam | Ensure the field name being referenced exists with exact spelling. |
| Lookup | The Data Extension name for a Lookup function call is invalid. A Data Extension of this name does not exist. Data Extension Name: Product | Ensure the Data Extension name is correct and the Data Extension was not deleted. |
| Lookup | The Lookup function call failed because the lookup field value (parameter 2) does not have a value Data Extension: Products Function Call: Lookup("Products",@price,"ProductName","Salesforce") | The second parameter, which is required, resulted in a null or empty value. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| LookupOrderedRows | The LookupOrderedRows function call failed because the target data extension for the lookup (parameter 1) does not resolve to a value. Function Call: LookupOrderedRows(@ProductDE,1,"CreatedDate Desc","ProductID",ProductID) | The first parameter does not have a value for Data Extension name. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| LookupRows | The Data Extension name for a LookupRows function call is invalid. A Data Extension of this name does not exist for the parent account. Data Extension Name: Products | When using the ENT prefix, the Data Extension name must be found at the enterprise account. The business unit referencing the Data Extension must also have permissions to access it. See Using AMPscript Language Elements with Enterprise Awareness for more details on the ENT prefix. |
| LookupRows | The Data Extension field name for a LookupRows function call is invalid. A field of this name does not exist. Function Call: LookupRows("Products","Brand", @BrandID) Data Extension Name: Products Field Name: Brand | The second parameter for Column Name does not exist in the Data Extension that is being called. Ensure the field names match exactly. |
| LookupRows | The LookupRows function call failed because the target data extension for the lookup (parameter 1) does not resolve to a value. Function Call: LookupRows(@ProductDE,"ProductID",ProductID) | The first parameter does not have a value for Data Extension name. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Mod | Invalid value specified for function parameter. Function Name: mod Parameter Name: Value1 Parameter Ordinal: 1 Parameter Type: Numeric Submitted Value: | The first parameter has an empty or null value. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| Multiply | Invalid value specified for function parameter. Function Name: Multiply Parameter Name: Value2 Parameter Ordinal: 2 Parameter Type: Numeric Submitted Value: | The second parameter has an empty or null value. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| RetrieveSalesforceObjects | Call to retrieve records for salesforceobject CustomObject__c failed! Error in the application. API Fault: Salesforce.com Fault thrown. Exception Type:InvalidSObjectFault Exception Code:INVALID_TYPE Exception Message:sObject type 'CustomObject__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names. | One reason this error might occur is the Salesforce System User does not have access to the object being Retrieved. Work with your Salesforce Administrator to ensure the necessary permissions are assigned to the Salesforce System User. |
| RetrieveSalesforceObjects | Call to retrieve records for salesforceobject Contact failed! The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. WebExceptionStatus: KeepAliveFailure | The call to retrieve Contact details failed due to a connection issue. There are potentially too many concurrent RetrieveSalesforceObject calls on the Contact object. The best practice recommendation is to use Synchronized Data Sources with a Lookup function instead. |
| RetrieveSalesforceObjects | No such column 'Product_code__c' on entity 'Contact'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. At row:1 and column: 121 | Ensure the name exists and is visible to the Salesforce System User. |
| Row | Invalid index (parameter 2) passed to Row function. Index must be less than or equal to the row count. Index Value: 1 Row Count: 0 Function: row(@Rowset, 1) | The rowset parameter returned an empty or null value. See this article for more details. |
| StringToDate | The date string to be parsed cannot be null or an empty string. Function Name: StringToDate Parameter Name: DateTimeString Parameter Ordinal: 1 Parameter Type: Text Submitted Value: | The first parameter has an empty or null value. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| StringToDate | String was not recognized as a valid DateTime. | Reference our Supported Date and Time Formats (ICU) |
| Substring | Invalid value specified for function parameter. Function Name: Substring Parameter Name: Length Parameter Ordinal: 3 Parameter Type: Numeric Submitted Value: -1 | Only a non-negative integer can be used for the length parameter. |
| Subtract | Invalid value specified for function parameter. Function Name: Subtract Parameter Name: Value1 Parameter Ordinal: 1 Parameter Type: Numeric Submitted Value: | A null or empty value was passed. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| SystemDateToLocalDate | Pasted data: The date to be converted cannot be null. Function Name: SystemDateToLocalDate Parameter Name: SystemDateTime Parameter Ordinal: 1 Parameter Type: Text Submitted Value: null | A null or empty value was passed. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
| TransformXML | Failed to parse XML document. See inner exception for details. XML Starts With: ORDER | The data passed to the TransformXML function is not in valid XML format. In this case, the starting element is ORDER instead of <ORDER> |
| UpdateDE | Value cannot be null. | A field being updated does not allow null values and the value being passed to UpdateDE function is null. Ensure any dynamically populated parameters have a value, or otherwise have logic to handle null or empty values. |
000393029

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.