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.

Recipe Error	Solution
Locating Unknown Errors	`Hmm, that didn’t work. Please try running the recipe again.` 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.
Triggered Object Data Sync	If the recipe triggered an object data sync, check whether the data sync failed and, if it did, review the errors.
Geolocation Fields	Remove unused geolocation fields in data sync. This field contains three parts: latitude, longitude, and a system field. You include latitude and longitude in input nodes and the SFDC_LOCAL Data Sync connection. They appear as `GeolocationFieldName__Latitude__s` and`GeolocationFieldName__Longitude__s`. High-precision numbers can result in a numeric overflow during ingestion and in computations. Specify a precision metadata override to avoid numeric overflows and other unexpected behaviors. Depending on your needs, set the precision to: 3 for locations accurate to within ~80 km. 5 for locations accurate to within ~800 m. 7 for locations accurate to within ~8 m. This precision is about the accuracy of most commercial GPS devices. 10 for locations accurate to within less than a centimeter. This level of accuracy requires specialized equipment. 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.
Numerical Overflows	`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.` 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. To resolve a numeric overflow error: Remove the longitude or latitude fields from the data source, data sync, dataflow, or recipe if they’re not functionally required. Adjust the numeric field’s precision and scale to accommodate the numeric value. Make sure that the field values are within the defined maximum and minimum values, including decimal places.