Answered

Page visibility after role change

(0) Share

Report

Posted on by bspangler

I'm providing support for a site that was set up to assign users to a custom web role after they initially sign up and are approved by one of the users in charge of the app/site. This web role is assigned via a Power Automate flow. Once this role is assigned, they should get access to a page on the Power Pages site that is only available to this custom web role.

However, some users are reporting that they still do not see this page even after they have been approved for several hours (in some cases, they have been approved for a day or more). The approval process is working as intended and the flow to assign the role is running instantly (as expected).

My first thought was that this was a caching issue, but the site's Cache-Control header is max-age=0. Clearing the browser cache and/or doing a "hard reset" (CTRL + SHIFT + F5) also do not solve the issue.

Why would the access/assigned role not be flowing all the way to the end user? And why would it only be happening to some users?

Categories:

Administer & monitor

General topics

Security

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Lucas001 2,529 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi @bspangler,

unfortunately it's an issue I had last year as well and which was not really solved to my knowledge.
There are several things I'd test:

Can you see the webroles assigned in the power pages admin center?

Can you see that the webrole is assigned within the page fetching it via Liquid?

The cache for power pages is quite settled. Usually up to 15 Minutes. You can try goign around with adding a condition filtering a string field on the current timestamp with liquid. Try that insvisible on the page you want people to come from.

If all these things do not work, create a Ticket for Microsoft. It has been an unconsistent bug which was changing behaviour a lot during the time from, don't cite me on that, I think 09/2024-04/2025. Was able to reproduce the error with my account during that time, having exactly the same behaviour; some users work fine, others not.

1 people found this reply helpful.

Was this reply helpful? Yes No
bspangler 15 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the suggestions and background info, @Lucas

Does this issue still happen to you, or did it go away for your site at some point?

I followed your recommendation and watched the Contact record in the Power Pages admin area. It worked normally when I tried, so the web role updated a few minutes after the flow ran, and the Power Pages site itself showed the correct pages about 1 minute after that (after doing a hard refresh).

Unfortunately, only a production version of this site was created, so I'm a little hesitant to try the troubleshooting with Liquid. If I ever decide to try that, what did you mean by adding a condition filtering a string field on the current timestamp?

I think my next steps will be to open a ticket with Microsoft if it gets consistent enough to reproduce on a call with them.

Was this reply helpful? Yes No
Lucas001 2,529 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @bspangler,

unfortunately we had users facing that issue a long time. But the problem itself became so inconsistent that I was not able to reproduce it anylonger.

The way we went is actually asking for a support request if one of the users experienced it again.

Here is an article of how to overcome caching with some tricks:

Power Pages: Cache test dummies – The ReadyXRM Blog by Nick Doelman

What I mainly refer to is this line:

<condition attribute="createdon" operator="on-or-before" value='{{ "today" | date: "yyyy-MM-dd HH:mm:ss" }}' />

Was this reply helpful? Yes No