In short: I have an Object Type, where some object instances are updated by the users.
When the object updates, the materialization dataset of this Object Type updates, as expected, as it propagated it in the pipeline.
However, I see that 1h later, there is another build triggering on the materialization dataset, even if no further updates were made by end users.
Is that expected ? Is there a way to avoid further builds in the pipeline to propagate because of this “ghost” build ?
..