How to fix the error - executeJobPreviewDataQuery no active stream for job=<job run id>

Pallavi Rajan Chincholkar 0 Reputation points
2023-09-13T10:25:59.92+00:00

Hello,

I am receiving this error while doing the Data Flow Data Preview in Debug.

User's image

It's not consistent. Sometimes it will appear at the first step, sometimes somewhere along the flow, for previewing data of as simple as a Select step.

We have checked the source and all other connectors, redid everything however the issue still remains unresolved.

Any guidance is highly appreciated.

Regards,

Pallavi

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,722 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. QuantumCache 20,266 Reputation points
    2023-09-15T04:11:17.6033333+00:00

    Hello @Pallavi Rajan Chincholkar Thanks for posting this query on this forum.
    Please do post the outcome from the support ticket on this forum, which will be helpful to other community members, thanks for your understanding!

    Some of the troubleshooting steps are:

    Sometimes the error was observed if we started using a conditional split transformation, but the issue was already addressed by the product team, if this is the case, then please do comment in the below section and we will be in touch with you to help further.

    If you do run into issues with loading a Flowlet, either using the refresh button within ADF or on the browser has been likely to resolve it.

    Derived column transformation to replace the flowlet and it works.

    Data preview for Flowlets is only supported in output transformation and requires that you specify all of the input data for that output transformation.

    1 person found this answer helpful.
    0 comments No comments

  2. Amira Bedhiafi 24,786 Reputation points
    2023-09-13T11:31:54.89+00:00

    The error in Azure Data Factory suggests an inconsistency in fetching or streaming data for preview. This can be due to transient network issues, hitting service limits, or issues with the source data. Ensure there are no connectivity issues on your end and that you're not exceeding any service quotas. Clearing your browser cache, trying different browsers, and refreshing metadata can sometimes solve these glitches. Additionally, enabling logging can provide more insight. If none of these solutions work, consider recreating the affected resources or reaching out to Azure Support for more specific assistance.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.