Stacks dependencies do not utilize last version of output

I have two stacks: A et B where B depends on A with the dependency “toto”.

The last applied performed on Spacelift led to “toto” output in stack A to be “value1”.

For some reasons I had to perform TF actions locally on the state of the stack A. After that I uploaded my state and sac in stack A in the output tab I can see that “toto” output is “value2” (which is right)

I ran a new run in stack A, no changes to be performed so NO APPLY ran (which is what I was expected after the local TF actions). I am now going to stack B which has been triggered by the stack A and see some wrongs changes in plan!!!! Stack B used “toto” with “value1” :(

After some time, I manually changed a value in one of my resources on my cloud provider linked to stack A. I triggered a run → plan and apply succeeded. This time stack B triggered with “toto” “value2” which is what I am expecting.

It seems that stack B does not directly use the output of stack A, but sort of the output value generated by the last applied ran and succeeded in stack A. While performing actions on the state and importing it (only plan with no changes triggered) it was really confusing! Maybe there should be a warning that the dependencies value is not ‘sync’ with the output anymore or something like that … Thanks