Hey @Sajjad Amiri thanks for the request! Someone from our solutions engineering team will reach out to see if we can get you a workaround.
Currently, this behavior is by design - stack dependencies only apply to tracked runs, not proposed runs (previews). This means preview runs execute in parallel and cannot access outputs that would be created by upstream stacks since those changes haven't been applied yet. I understand this makes it difficult to see the full impact of changes across your dependent stacks.
Log in to comment and vote
Comments1
Natalia Gazda
Aug 5, 2025
Hey @Sajjad Amiri thanks for the request! Someone from our solutions engineering team will reach out to see if we can get you a workaround.
Currently, this behavior is by design - stack dependencies only apply to tracked runs, not proposed runs (previews). This means preview runs execute in parallel and cannot access outputs that would be created by upstream stacks since those changes haven't been applied yet. I understand this makes it difficult to see the full impact of changes across your dependent stacks.