Forum Discussion
Long runtime and NA table
Hello,
When I check the refresh history for a couple of dataflows gen2, I see that the first step is always like this, Table name: NA. It always takes the longest time to run compare to others table. What is this?
In this example it tooks only 3m but in others it can take 10-15m
Hi debosul
Thanks for using Fabric Community.
This is an expected behaviour.- Not a Physical Table: The "Table name: NA" step doesn't represent a concrete table in your dataflow. It's a placeholder for initial setup and orchestration tasks.
- Common Tasks:
- Initializing source connections
- Extracting metadata
- Optimizing dataflow logic
- Validating data structures
- Creating temporary staging resources
Potential Reasons for Long Duration:
- Complex Dataflows: Extensive data sources, intricate transformations, or large datasets can prolong this step.
- External Dependencies: Reliance on external services or slow-responding systems can create delays.
Hope this helps. Please let us know if you have any further questions.
2 Replies
Hi debosul
Thanks for using Fabric Community.
This is an expected behaviour.- Not a Physical Table: The "Table name: NA" step doesn't represent a concrete table in your dataflow. It's a placeholder for initial setup and orchestration tasks.
- Common Tasks:
- Initializing source connections
- Extracting metadata
- Optimizing dataflow logic
- Validating data structures
- Creating temporary staging resources
Potential Reasons for Long Duration:
- Complex Dataflows: Extensive data sources, intricate transformations, or large datasets can prolong this step.
- External Dependencies: Reliance on external services or slow-responding systems can create delays.
Hope this helps. Please let us know if you have any further questions.
Hi debosul
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
Otherwise, will respond back with the more details and we will try to help.
Thanks