Share via

Azure Data Factory Dataflow job failed due to reason: not started

Patrick Wong 0 Reputation points
2023-04-05T23:39:48.0233333+00:00

Hello everyone, I have an ADF job which will be triggered hourly with a concurrency of 9. However, I always have a few failed jobs out of 9 and they came with the following error: {"StatusCode":"DFExecutorUserError","Message":"Job failed due to reason: Not started","Details":"java.lang.Throwable: Not started\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1$$anonfun$2.apply$mcV$sp(FlowRunner.scala:201)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1$$anonfun$2.apply(FlowRunner.scala:194)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1$$anonfun$2.apply(FlowRunner.scala:194)\n\tat scala.util.Try$.apply(Try.scala:192)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1.apply$mcV$sp(FlowRunner.scala:194)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1.apply(FlowRunner.scala:185)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1.apply(FlowRunner.scala:185)\n\tat scala.util.Try$.apply(Try.scala:192)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply$mcV$sp(FlowRunner.scala:185)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply(FlowRunner.scala:177)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply(FlowRunner.scala:177)\n\tat scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Futur"} Upon some reruns it will eventually be successful. However, this is a very irritating error message as I cannot know what is exactly going on. A failed job is successful after some reruns, so I guess the job itself is error free. Any help will be appreciated, thank you in advanced. Best regards, Patrick

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.


3 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Bhargava-MSFT 31,361 Reputation points Microsoft Employee Moderator
    2023-04-07T19:15:28.9066667+00:00

    Hello Patrick Wong, Welcome to the MS Q&A platform. As you mentioned, the job succeeded after multiple runs; it seems like this is a transient issue. Can you please tell me when did you notice the issue for the first time? Is this specific to a single pipeline? A similar thread has been discussed on the below URL. Please follow the steps mentioned in the answer section and see if it helps. https://learn.microsoft.com/en-us/answers/questions/959963/azure-synapse-error-job-failed-due-to-reason-not-s

    Was this answer helpful?

    0 comments No comments

Your answer

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