Custom (Approved) App: Scenario Still Shows Old Module Schema After Update

Questions
1

:bullseye: What is your goal?

Change the Custom Webhook Configuration in a Custom Approved App, internally test it, and publish it.

:thinking: What is the problem & what have you tried?

After having admin rights for the custom app transferred internally, critical changes to a webhook in the app are not reflected in the modules in the scenario. In other words, even when using the account that has admin rights for the custom app, I cannot test the changes I have made to the webhook module.
For that reason currently internal testing and publishing the updated webhook is blocked.
The issue is very similar to the one described in following discussion: Custom App: Scenario Still Shows Old Module Schema After Update - #13 by Clearout.

5

“Thanks for sharing this! I’ve seen similar issues when admin rights are transferred — the scenario editor sometimes keeps showing cached data even after updates. Refreshing or re-syncing the app metadata usually fixes it. Your explanation makes it much easier to understand what’s going on.”