pipeline failed due to reason Job failed due to reason: None.get

Vasudeva Sreeramadasu 0 Reputation points
2023-10-16T08:22:16.88+00:00

I am getting below error in once of my dataflow activity.

Operation on target co_case_request1 failed: {"StatusCode":"DFExecutorUserError","Message":"Job failed due to reason: None.get","Details":"java.util.NoSuchElementException: None.get\n\tat scala.None$.get(Option.scala:529)\n\tat scala.None$.get(Option.scala:527)\n\tat com.microsoft.dataflow.transformers.FoldDownPlanner$.unrollNode(FoldDown.scala:800)\n\tat com.microsoft.dataflow.transformers.FoldDownPlanner$.$anonfun$physicalPlan$16(FoldDown.scala:615)\n\tat scala.util.Success.$anonfun$map$1(Try.scala:255)\n\tat scala.util.Success.map(Try.scala:213)\n\tat com.microsoft.dataflow.transformers.FoldDownPlanner$.$anonfun$physicalPlan$12(FoldDown.scala:588)\n\tat scala.util.Success.flatMap(Try.scala:251)\n\tat com.microsoft.dataflow.transformers.FoldDownPlanner$.$anonfun$physicalPlan$9(FoldDown.scala:576)\n\tat scala.util.Success.flatMap(Try.scala:251)\n\tat com.microsoft.dataflow.transformers.FoldDownPlanner$.physicalPlan(FoldDown.scala:533)\n\tat com.microsoft.dataflow.FlowRunner$$anon$2.$anonfun$traverseStreamGroup$16(FlowRunner.scala:1073)\n\tat com.microsoft.dataflow.FlowRunner$$anon$2.$anonfun$traverseStreamGroup$16$adapted(FlowRunner.scala:1062)\n\tat scala.collection.immu"}

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,484 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,773 questions
{count} votes

1 answer

Sort by: Most helpful
  1. BhargavaGunnam-MSFT 27,661 Reputation points Microsoft Employee
    2023-10-18T20:23:17.74+00:00

    Thanks @Vinodh247-1375

    Vasudeva Sreeramadasu,

    A similar issue has been discussed here

    The errors you are seeing are intermittent and they are resolved now.

    If you are still getting the error, please let us know.

    I hope this helps.

    0 comments No comments