Restarting Your Power Pages Portal
Audience: System Administrators, Portal Administrators
Summary
If your Work 365 Self-Service Portal shows “Error loading control,” missing/duplicated navigation, or stale content after recent changes, a site restart usually resolves it by refreshing cached configuration and reloading the portal service. Use a restart for deeper issues; use Clear website cache for minor content updates.
When to Restart the Portal
Restart the portal if you observe any of the following:
“Error loading control” messages.
Recent web page / site map changes not appearing on the live site.
Navigation items broken, duplicated, or missing.
Performance or caching issues that persist after publishing changes.
Template, snippet, or CSS updates not reflected on the site.
Tip: A restart is deeper than Clear website cache. It reloads the entire portal service instance and typically takes 2–5 minutes.
Steps to Restart Your Portal
Open Power Platform Admin Center
Go tohttps://admin.powerplatform.microsoft.comand sign in with a Global Administrator, Power Platform Administrator, or an account with Power Pages site admin permissions.Select the Environment
In the left navigation, choose Environments, then open the environment that hosts your Work 365/Power Pages site.Locate the Portal / Power Pages Site
Under Resources → Power Pages sites (or Apps), find your portal (e.g., Contoso Customer Self-Service Portal) and open it.Restart the Portal
In the site’s management view, open Site actions (or Actions) → Restart site → Confirm.
During the restart, users may briefly see a Service Unavailable message.
Allow 2–5 minutes for the site to come back online.
Verify the Portal
Open your portal URL and confirm that pages load, controls render, menus appear correctly, and your recent configuration or styling changes are visible.
If the issue persists, perform a hard refresh (Ctrl/Cmd + Shift + R) or test in a private/incognito window.
Optionally run Site actions → Clear website cache for an additional refresh.
Precautions & Best Practices
Do:
Restart during off-peak hours to minimize user impact.
Ensure you have appropriate admin permissions.
Notify users if restarting during business hours.
Clear browser cache after the restart to avoid stale assets.
Don’t:
Restart repeatedly without cause.
Restart multiple portals simultaneously in the same environment.
Trigger back-to-back restarts—wait for one to complete first.
Confuse Clear website cache (lighter action) with a full restart—use cache clear for minor content/list updates.
Tip: Try Clear website cache first for simple page/list/translation updates; escalate to Restart site if issues remain.
Troubleshooting After Restart
If problems persist after a successful restart:
Browser & client cache: Hard refresh or test in a private window.
Recent deployments: Ensure changes are published and any table permissions are correct.
Environment health: Check the Admin Center for service advisories or API throttling.
Security/visibility: Verify web roles, access control rules, and table permissions for data-bound pages.
Work 365 specifics: If your issue is limited to Work 365 components (e.g., subscription lists), confirm Display on Portal flags and related visibility settings, then clear cache again.