TF cloud speculative plan triggers for many unrelated workspaces

We have a single repo for our aws infrastructure. It has many folders.
Each folder is associated with a different terraform workspace.
workspaces are configured to only trigger runs when files in a specified path change.
We configure this workspaces to trigger speculative plans.
Developer works on a specific folder and makes terraform changes.
In the past when we created a PR speculative plan was only triggering for the files they changed in a specific directory.
Now we see speculative plans are triggered for all the workspaces associated with a repository.
This is confusing for developers because they only changed files in one folder and were expecting to see the speculative plans for the files they changed.

This started happening recently. Is there a way to limit speculative plans to be triggered for a specified path?


1 Like

Any update on this how can we do solve this issue?