Sourcing Rule Loops and PRs Generated in Incorrect Organizations

Summary:

How does Fusion SCP handle loop detection in sourcing rules across multiple organizations? When configuring sourcing rules to check for excess stock across shared organizations, we are encountering circular references that result in PRs being generated in the wrong organization.

Content (please ensure you mask any confidential information):

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):