Azure Synapse Mapping Dataflow - Job failed due to reason: Not started.

Christopher Geckert 91 Reputation points
2022-08-12T14:01:27.603+00:00

Hello,

since yesterday we've got an issue with two mapping Data Flows in Azure Synapse:

{"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.apply$mcV$sp(FlowRunner.scala:175)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1.apply(FlowRunner.scala:168)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1$$anonfun$1.apply(FlowRunner.scala:168)\n\tat scala.util.Try$.apply(Try.scala:192)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply$mcV$sp(FlowRunner.scala:168)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply(FlowRunner.scala:160)\n\tat com.microsoft.dataflow.FlowCode$$anonfun$run$1.apply(FlowRunner.scala:160)\n\tat scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)\n\tat scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)\n\tat scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)\n\tat scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)\n\tat scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:133","failureType":"UserError","target":"Data flow1","errorCode":"DFExecutorUserError"}

Is there any issue with the debug clusters or something like that? Also from time to time the Pipes and Dataflow just don't start and Queue forever.

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,346 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,487 questions
{count} votes

1 answer

Sort by: Most helpful
  1. BhargavaGunnam-MSFT 25,881 Reputation points Microsoft Employee
    2022-08-17T21:35:46.363+00:00

    Hello @Christopher Geckert ,

    The product team identified the problem and they are working on it. I will keep you posted once the fix is applied.

    Latest Update on Aug 17th, 2022: This issue is being hot fixed by the product team today. If you ever notice this issue, please feel free to let us know. Thank you for your patience.