Loading
About Salesforce Data 360
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Troubleshoot Activation Errors

          Troubleshoot Activation Errors

          Get tips for solving common activation errors in Data 360.

          Error Troubleshooting Suggestions
          Required fields don't have a value
          • Complete the required fields
          Invalid email address
          • Use an email address with an @ and .
          • Use an email address that's fewer than 254 characters
          Invalid date
          • Use a date as MM/DD/YYYY or DD/MM/YYYY
          Invalid locale
          • Use a locale to define the country of the subscriber. For example: A resident of the U.S. who speaks English would receive the en-US locale value
          Invalid phone
          • Use a phone number as ###-###-####
          • Use a phone number with the correct country code number
          Field not found
          • Determine if the field still exists in the data extension. Modify the field mapping if the data extension schema changes
          Bucket or directory not found
          • Confirm that the bucket name (GCS) or container name (Azure) is present and spelled right in the target region.
          • Provide a valid and accessible directory path with necessary permissions.
          • Ensure that the request parameters in your configuration match the requirements of the destination storage account.
          Invalid field count
          • When you import a data extension, make sure the number of fields is correct
          Invalid decimal
          • Use a value within the length range. For example: The length is 3 and the value is XXX or XX.X
          Connectivity issue at the SFTP server
          • Check that the SFTP server is online and has a stable network connection.
          • Verify that the server is scaled to handle new connection requests.
          • Confirm that your firewall or security rules aren't blocking Salesforce IP addresses.
          • Retry after some time.
          Connectivity issue with cloud storage service
          • Check that the cloud storage service (Google Cloud Storage or Azure Blob Storage) is online and has a stable network connection.
          • Confirm that your cloud provider's firewall or virtual network (VNet) rules aren't blocking Salesforce IP addresses.
          • Ensure the GCS or Azure activation target is enabled and connected, and the activation definition is active.
          • Retry after some time.
          SFTP permission or protocol issue
          • Check that the SFTP username and password/SSH keys are accurate and up-to-date.
          • Ensure the SFTP user has the necessary permissions for the target directory on the SFTP server.
          • Confirm that the SFTP server is running a compatible SSH/SFTP protocol version.
          • Investigate any network interruptions or unstable connections between the application and the SFTP server.
          Authentication or permission issue
          • Check that the access key, shared access signature (SAS), or service account credentials are accurate and up-to-date.
          • Ensure the authenticated user/principal has the necessary write/edit permissions for the target container or bucket.
          • Confirm that the credentials are valid.
          • Investigate if specific IP restrictions on the cloud account are rejecting the connection.
          File or data format issue
          • Ensure that the file isn't modified, moved, or deleted while the activation is in progress. Check the activation status via the UI or Connect API.
          • Verify that the file compression format (for example, .GZIP) is supported by your configuration and the destination.

          Activation and Segment Count Differences

          Due to various factors, there can be differences between your activation and segment count.

          • Segmenting and activating on different objects: To avoid different counts, activate on the same object.
          • Data is coming from two or more data streams: Check your data mapping from the DLO and DMO.

            If the Individual ID comes from two data streams but has attributes mapped to different fields in the DMO, it can lead to duplicate records.

            Segmentation does a distinct count on Individual IDs. If there are duplicate IDs, segmentation counts that ID one time. In activation, if there are multiple records of the same ID and the same values in the attributes, it's deduped.

          • Multiple records from activating on Unified data model object (DMO): Activate on a non-Unified DMO or don’t select an attribute with an N:1 relationship.

            If you’re activating on a Unified DMO and selecting direct attributes, check the relationship between the Activate on object and the activated DMOs. If any DMOs have an N:1 relationship, there may be multiple records.

           
          Loading
          Salesforce Help | Article