---
schema_version: "1"
id: 9e0046b40dcf6c95f45966e3bc60cc761c039964d3726242ae4cb257b6bf4320
title: Troubleshoot Segment Errors
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_segmentation_troubleshooting.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_segmentation_troubleshooting.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 891949150bf52b1c682e6750f3d5ca3e4960510b09b498f3b3a79f4a68eebff3
description: Get tips for solving the most common segment errors in Data 360.
products:
  - Data 360
release: "264"
---
# Troubleshoot Segment Errors

Get tips for solving the most common segment errors in Data 360.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d214228e39">Error</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d214228e42">Troubleshooting Suggestions</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment references too many data lake objects (DLOs).</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Use a Calculated Insight (CI) to reduce the number of DLOs referenced by your
                segment.</li>

              <li>Split a segment into multiple smaller segments.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment is too complex.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Use a CI instead of many attributes and nested operators.</li>

              <li>Use a CI instead of an attribute (data model object) with many relationships.</li>

              <li>Combine text values into one <code>Is In</code> text operator.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment returns skewed data.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Remove placeholder values like <kbd>0</kbd> or
                <kbd>Unknown</kbd> from source data before ingesting data into <span>Data 360</span>.
              </li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment is inactive.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Copy the inactive segment to create a segment with the same population.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Too many segments are trying to publish at the same time.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Wait for some segments to finish publishing and try again.</li>

              <li>Change the publish schedule for some of your segments.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment population recount in progress.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Wait for the recount to finish and try publishing the segment again.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment wasn’t processed.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Contact Salesforce Customer Support for help.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Multiple population counts are in progress. </td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Wait for the counts to complete and try again.</li>

              <li>Improve the segment by making it simpler, using nested segments, or merging the
                containers, if possible.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment population count failed.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Identify containers with the same join paths and merge them using nested operators, if
                possible.</li>

              <li>Avoid long paths and use the shortest join path to reach the needed attribute.</li>

              <li>Avoid cyclic paths in segments. Cyclic paths are relationships that use cyclic behavior
                (a→b→a). While segment counts can fail, segment jobs can run successfully.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment can’t be published.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Simplify your segment by merging containers when possible. Use nested operators to merge
                the containers.</li>

              <li>Ensure the DMO types are correct, especially for Engagement Type data. Incorrect DMO
                types can cause timeouts and failures.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Segment count/population mismatch.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Segmentation applies a filter on the engagement date (24 months for standard segments
                and 7 days for rapid segments). In Data Explorer, make sure to apply the filter on the
                engagement event date.</li>

              <li>Ensure date operators match with tenant timezones.</li>

              <li>Check if the source data has drastically changed (significant additions, updates, or
                deletions).</li>

              <li>If you use Calculated Insights in your segments and notice an unexpected increase or
                decrease in segment count or segment population, check if any Identity Resolution rules
                were processed between the CI and segment run.</li>

              <li>Segmentation in Data 360 generates a list of unique profile IDs as output. But
                Marketing Cloud uses the Subscriber Key attribute for segmentation; hence, the
                population counts in Data 360 and Marketing Cloud can differ.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e39 ">Unable to edit segment, or segment editor UI times out.</td>

          <td data-label="Troubleshooting Suggestions" class="slds-cell-wrap" style="vertical-align:top;" headers="d214228e42 ">
            <ul>
              <li>Remove unnecessary relationships defined at Segment On at the DMO level. If the issue
                persists, contact Salesforce Customer Support for help.</li>

            </ul>
          </td>

        </tr>
      </tbody>
    </table>

#### See Also

- [_Salesforce Help_: Calculated Insights in Segments](https://help.salesforce.com/s/articleView?id=data.c360_a_calculated_insights_in_segments.htm&release=264.0.0&type=5 "Use a calculated insight to control data-driven insights in segmentation. You can also describe the calculated insight’s metrics and dimensions in a segmentation filter.")
- [_Salesforce Help_: Data Objects in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_objects.htm&release=264.0.0&type=5 "When working with Data 360, it’s helpful to know about Data 360 data objects including data lake objects (DLO) and data model objects (DMO).")
- [_Salesforce Help_: Data Model Objects](https://help.salesforce.com/s/articleView?id=data.c360_a_data_model_objects.htm&release=264.0.0&type=5 "Create, view, and manage data model objects (DMOs). DMOs are fundamental to Data 360. Familiarize yourself with the definitions, concepts, and resources related to DMOs before creating or working with them.")
- [_Salesforce Help_: Publish a Segment in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_publish_segment.htm&release=264.0.0&type=5 "After defining your segment in Data 360, you can publish it to your activation targets whenever you want or based on a schedule when the segment was created. The standard publish schedule is 12 or 24 hours. You can also change the segment schedule by editing its properties. When you’ve reached the segment publish concurrency limit, Data 360 defers the publish of other segments. This deferral continues until the number of simultaneously running segments falls below the limit. This means that a segment scheduled at a specific time sometimes doesn’t start publishing at its scheduled time.")