Forum Discussion

michaelfabric's avatar
michaelfabric
Frequent Visitor
2 months ago
Solved

dbt job pipeline activity: bug

Hi everone,   The operation (like run, build and compile, under "Advanced Settings") of a dbt job activity in a pipeline is not being pushed to the repo when doing a commit. As a result, my fabric-...
data engineering
data pipeline
  • michaelfabric's avatar
    michaelfabric
    1 month ago

    I created a support ticket and have the following update to share: Microsoft support has excalated this issue and a fix will be implemented:

    "We have done further tests on this internally and were able to reproduce the behavior. Then escalated it internally to our Product team. As a result, this will be addressed and the current tentative for the fix is in September. 

    If things go as planned, it should be during the first week of September but deployment can vary depending on different regions."

     

    Please check the reply of ryan-schofield for a temporary workaround.

Prince0011's avatar
Prince0011
Icon for Solution Sage rankSolution Sage
1 month ago

Hi User,

Based on your description, this appears to be a product issue with the serialization of the dbt Job Pipeline Activity configuration during Git commits.

Since the Operation setting (for example, run, build, or compile) isn't being persisted to the repository, downstream CI/CD deployments recreate the pipeline without this required property, which then causes the activity to fail at runtime.

As a workaround, you can:

  • Verify whether the issue occurs across multiple workspaces and repositories to rule out a workspace-specific configuration.

  • Check if you're using the latest Fabric experience, as this may have been addressed in a recent update.

  • Continue using the manual JSON edit temporarily, although as you've observed, Fabric currently removes the operation property during the next synchronization.

  • If the behavior is consistently reproducible, collect the pipeline JSON, deployment logs, and Git commit history, then open a Microsoft Support ticket, as this appears to be a product bug rather than a configuration issue.

For more information:

Could you also confirm:

  • Does this occur for all dbt operations (run, build, and compile) or only specific ones?

  • Is the issue reproducible in a newly created pipeline?

  • Which Git provider are you using (GitHub or Azure DevOps)?

If others in the community can reproduce the same behavior, it would help confirm whether this is a broader product issue affecting dbt pipeline activities.

 

 

💡 Helpful? Give a Kudos 👍 — keep the community growing.

✅ Solved your issue? Mark this as the Accepted Solution ✔️

Best regards,
Prince Singh | Data Science & Microsoft Fabric Enthusiast