---
schema_version: "1"
id: 631f5586f33cfdec680a6406e2d49ef33a15aa7c91b926d436329778bb12fd59
title: Recipe Inspector Scenarios
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_job_recipe_inspector_scenarios.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_job_recipe_inspector_scenarios.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bf5fceb6987948e107bb26c7889a69ae9b4ae990962c813fc68da0e1c54c10d3
description: The CRM Analytics recipe inspector details provide information about the complexity of runtime processing. The following are common scenarios seen in the recipe inspector and what they mean.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Recipe Inspector Scenarios

The CRM Analytics recipe inspector details provide information about the complexity of runtime processing. The following are common scenarios seen in the recipe inspector and what they mean.

## `0` Rows Out

0 Rows Out during recipe execution occurs for various reasons. One common reason is because the recipe performs the data load from a previous stage or source and operations “in place.” Therefore, the stage records no output rows. These “in place” transformations are necessary to perform the next steps.

![Shows a "zero rows out" scenario in the recipe inspector details.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi_integrate_recipe_inspector_zero_rows_out.png)

## Multiple Recipe Nodes in One Stage

The stage name value may show one node name or a comma-delimited list of node names. When a list of node names is present, it represents the recipe nodes that ran together for optimization purposes.

![Shows a "multiple nodes in one stage" scenario in the recipe inspector details.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi_integrate_recipe_inspector_multi_nodes.png)

## Internal Stages

Internal stages represent data prep work done before actual executions, such as joins or aggregations. They run separately and can have time costs associated with them.

![Shows an "internal stages" scenario in the recipe inspector details.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi_integrate_recipe_inspector_internal_stages.png)

## Cached Reads

If the input dataset is a staged dataset, recipe execution treats the read of one entire dataset as one row. Caching staged datasets optimizes performance. The node reports one row in because reporting the correct row count requires additional performance overhead. The counts for the rows out are usually accurate.

![Shows a "cached reads" scenario in the recipe inspector details.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi_integrate_recipe_inspector_cached_reads.png)