Hi,
From what I learned, different workspaces are treated independently and especially with different schedule, data should be refreshed well or at least the latest good partition of dataset wo...
Hi
Yes I am facing the same problem, the current workaround is to not rely on linked dataflows (unload them) and reference an upstream dataflow in the same workspace in the M code (so dataflows think it cannot be skipped in the refresh)
If you check the refresh history you can see the linked dataflow was skipped (assuming the data from the earlier refresh has been pushed into this linked dataflow but clearly the linked dataflow holds stale data)
The problem is linked dataflows between workspaces do NOT always hold the same data and if this was the case, then the orchestration of refreshes would work correctly.