401 after automatic scope update

So, I built a custom connection to a Microsoft Dynamics app, which works, except…

The connection’s scope keeps updating from:

https://mytenantname.crm4.dynamics.com/.default , which it should be, to

https://mytenantname.crm4.dynamics.com/.default,https://mytenantname.crm4.dynamics.com

So it basically re-adds the base URL without the scope to the end of the scope, separated with a comma.
It does this every so often (I think ~every 10 minutes). After this, any modules that use this connection will throw a 401 error, because it obviously doesn’t recognize the scope. When I then go back into the Connection and try to Re-authorize, I get this:

I can fix it manually by just editing the Connection, changing nothing and saving it, then re-authorizing. But obviously I want my scenario to run on autopilot and not have to go in every time to change it.

Any ideas what may be causing this, and how I can fix it?

For complex technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.

You can open a new ticket, or if you are unable to login for some reason, you also can reach support using the contact form on the website.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

2 Likes

I tried that, but since it is a custom connection and HTTP request module, they won’t support on it. I was hoping someone had similar experience here and have an idea on how to fix it.