Styled Content Widget is generating RCA with same Source and Target Scopes that fail to be Allowed by adminDescriptionWhen adding a new widget instance to a page outside of Content Publishing scope (such as Content Experiences), if the widget instance is also not Content Publishing scope but instead the same scope as the page (such as Content Experiences), an RCA will be created upon adding a Content Publishing widget (via Schedule Content) to that widget instance and loading the page. This RCA will have the target scope and source scope both be the non-Content Publishing scope (such as Content Experiences) and will not be able to set as "Accepted". In addition, the widget will not be visible on the page as the RCA error will be preventing it from showing up. An admin user is not able to Allow Styled content related RCA. An admin should be able to Allow all RCAs in correct scope, or no RCAs should be created in the first place.Steps to Reproduce 1. Ensure Content Publishing and Content Experiences (with demo data) are both installed2. Set your scope to "Content Experiences"3. Create a widget instance in the content_automation_demo page for Styled Content widgets4. Give this widget instance a title, and ensure the Application scope is still Content Experiences5. Create a styled content in "Portal Content"6. Schedule the styled content you created in step 5 into the widget instance you created in step 3 adding an appropriate audience such as "Active Users"7. Visit the content_automation_demo page and notice RCA errors8. Go to the platform and try to resolve the new RCA by marking it as Accepted The system does not allow to edit it and says that Source and Target scope cannot be the same. Notice source and target scopes are both Content Experiences.WorkaroundThis problem is targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. You can avoid this problem by creating all new widget instances using the Content Publishing scope. Simply by following the Steps to reproduce above in Content Publishing scope, no RCAs will be created and no errors will occur. Content will load normally.Related Problem: PRB1528108