---
schema_version: "1"
id: 831385b61a558eb21d648db22be5dfcc1895d9a0b30756fc237fb5c810ffccc9
title: Why am I receiving recipe errors?
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_troubleshoot_recipe_errors.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_troubleshoot_recipe_errors.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b0088795713d96dd4425fe006d8c2c39b842e4cea0862ce997bcf5bd8af47034
description: These suggestions can help resolve recipe errors in CRM Analytics.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Why am I receiving recipe errors?

These suggestions can help resolve recipe errors in CRM Analytics.

When troubleshooting a recipe error, use the org where the error occurred. A recipe can work differently depending on the org. For example, a recipe that works in a sandbox can work differently in production because that org can contain more data, different foreign keys, or unexpected values.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:28.49002849002849%">
          <col style="width:71.5099715099715%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d71113e42">Recipe Error</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d71113e45">Solution</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Recipe Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e42 ">Locating Unknown Errors</td>

            <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e45 ">
              <pre class="line-numbers slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium slds-scrollable_x"><code>Hmm, that didn’t work. Please try running the recipe again.</code></pre>
              <p style="margin-bottom:0;">When a recipe fails, but the error isn’t identified, like break the recipe into
                smaller recipes to pinpoint where the error occurs. Fix the error and try
                again.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Recipe Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e42 ">Triggered Object Data Sync</td>

            <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e45 ">If the recipe triggered an object data sync, check whether the data sync failed
              and, if it did, review the errors.</td>

          </tr>
          <tr class="">
            <td data-label="Recipe Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e42 ">Geolocation Fields</td>

            <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e45 ">
              <p>Remove unused geolocation fields in data sync. This field contains three parts:
                latitude, longitude, and a system field. </p>
              <p>You include latitude and longitude in
                input nodes and the SFDC_LOCAL Data Sync connection. They appear as
                <kbd>GeolocationFieldName__Latitude__s</kbd> and<kbd>
                  GeolocationFieldName__Longitude__s</kbd>. High-precision numbers can
                result in a numeric overflow during ingestion and in computations.
              </p>
              <p>Specify a
                precision metadata override to avoid numeric overflows and other unexpected
                behaviors. Depending on your needs, set the precision to:</p>
              <ul>
                <li>3 for locations accurate to within ~80 km.</li>
                <li>5 for locations accurate to within ~800 m.</li>
                <li>7 for locations accurate to within ~8 m. This precision is about the accuracy
                  of most commercial GPS devices.</li>
                <li>10 for locations accurate to within less than a centimeter. This level of
                  accuracy requires specialized equipment.</li>
              </ul>
              <p style="margin-bottom:0;">Latitude values are between -90 and 90, and 0 is the equator. Longitude
                values are between -180 and 180, and 0 is the prime meridian.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Recipe Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e42 ">Numerical Overflows</td>

            <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e45 ">
              <pre class="line-numbers slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium slds-scrollable_x"><code>The job completed, but some rows failed. Download the error log from the data monitor to view the failed rows and the reasons they failed.</code></pre>
              <p>If you get a warning that some rows have failed, it could be due to numerical
                overflows. For example, the numeric field value exceeds the maximum number of
                decimal places. Review the error log to locate the failed rows.</p>
              <p>To resolve a numeric overflow error:</p>
              <ul>
                <li>Remove the longitude or latitude fields from the data source, data sync,
                  dataflow, or recipe if they’re not functionally required.</li>

                <li>Adjust the numeric field’s precision and scale to accommodate the numeric
                  value.</li>

                <li>Make sure that the field values are within the defined maximum and minimum
                  values, including decimal places.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Recipe Error" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e42 ">&nbsp;</td>

            <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d71113e45 ">&nbsp;</td>

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