Loading

CRM Analytics Recipe Preview Timeout and Error 2006: Causes and Resolutions

Publish Date: May 26, 2026
Description

When building or editing a Data Prep recipe in CRM Analytics, the preview fails to load and displays Error 2006 or the message “Preview timed out.” The recipe editor becomes unresponsive and you cannot validate your transformation logic. This issue affects admins and developers working with large datasets, complex transformation chains, or recipes sourcing data from multiple connections.

Why the preview may fail to load

Large Dataset or High Row Count

Recipe preview runs against the first rows of the connected dataset. When the source object has a very large number of rows or fields, the preview query times out before returning results. The full recipe run can still succeed even when preview fails.

Complex Transformation Chain

Recipes with many sequential transformation nodes (formula fields, filters, lookups, appends) require more computation for each preview step. Previewing from a node deep in the chain forces CRM Analytics to re-evaluate all upstream transformations, which may exceed the preview timeout.

Input Caching Serving Stale Data

By default, recipe previews may use cached input data. If the cache is stale or corrupted, the preview can fail or return incorrect results. Disabling input caching forces a fresh data pull and resolves some Error 2006 occurrences.

Missing or Renamed Field in Data Sync

If a field referenced in the recipe was removed from the data sync configuration, renamed, or had its field-level security changed for the Integration User, the preview fails when it attempts to access that field. The error may appear as Error 2006 or as a validation error on the affected node.

 

Resolution
Step 1: Run the recipe instead of previewing

Recipe preview is optional. If preview times out but the recipe logic is correct, run the full recipe job from Data Manager > Recipes. The full run operates against the complete dataset with a longer timeout and may succeed where preview fails. Monitor the job in the Jobs Monitor tab.

Step 2: Disable input caching

In the recipe editor, open the recipe settings and disable input caching. Then retry the preview. Disabling caching forces CRM Analytics to pull fresh data and can resolve timeouts caused by a stale or inconsistent cache state.

Step 3: Identify and remove missing field references

In the recipe editor, look for nodes highlighted in red or orange. A red node indicates a broken reference — typically a field that no longer exists in the connected dataset. Click the affected node and either update the field reference or remove the step. In Data Manager > Connect, verify that the field is still enabled in the data sync configuration for the relevant object.

Step 4: Preview from an earlier node

Instead of previewing the entire recipe, preview from a node earlier in the transformation chain to isolate where the timeout occurs. Narrow down the problematic node, then simplify or split that step.

Step 5: Split complex recipes

If the recipe has more than 15–20 transformation nodes or combines data from more than 3 connections, consider splitting it into two smaller recipes where the first recipe outputs an intermediate dataset used by the second.

Note: If Error 2006 persists after all steps above, collect the recipe JSON (download from Data Manager > Recipes > Actions > Download), the job ID from the Jobs Monitor, and your org ID before contacting Salesforce Support.

FAQ

My recipe preview shows Error 2006 but the full recipe run succeeds. Is this normal?

Yes. Preview and full run have different timeout thresholds. If the full run succeeds, the recipe logic is correct. You can skip preview for that recipe and rely on the full run to validate output.

The recipe was working yesterday. Why is it failing with Error 2006 today?

Check whether a field referenced in the recipe was recently removed from the data sync, had FLS changed for the Integration User, or was renamed in the Salesforce org. Any of these changes can cause a recipe that previously worked to fail.

Can I schedule the recipe even if preview fails?

Yes. You can save and schedule a recipe regardless of preview status. The schedule runs the full recipe job, which has a longer timeout than preview.

Knowledge Article Number

005385254

 
Loading
Salesforce Help | Article