Failed to deploy changes for some outputs

Ask the Community
1

Hi,

I have a production pipeline and the environment is locked. Whenever the upstream data source is updated, the schedule triggers the build. The build succeeds, but the transaction is aborted, i.e, no data is written to the dataset.

When I unlocked the env and then trigger build, transaction is successful and data is written.
How do I fix this issue? I want production environment to be locked.

Screenshot 2026-09-24 at 10.13.45 PM
Screenshot 2026-09-24 at 10.13.45 PM626×162 57 KB

2

Is this an incremental or snapshot (or streaming) pipeline? Are the transactions aborted because there are no new data to add to your output? Also confirming that no logic is changing it’s just the input dataset that is updating?

3

This is incremental pipeline. There is data to update but the data isn’t updated because env is locked. When I unlock the env and retrigger the build, the data is updated. No logic change.

4

Any update on this? @helenq

5

Hey @manangoel sorry for the delay! It’s a bit hard for me to debug what’s going on with the current information so some follow up questions:

  1. If you trigger the build off of the dataset instead of the schedule (outside of pipeline builder) does it succeed? Or does it also abort
  2. Are you able to share a screenshot of the schedule that you have configured (the side panel)? Wondering if you have anything checked off in the advanced options
  3. If possible would be helpful to see the build history of the output in question as well