I am facing an issue with the Explore Data landing page in a Pega Constellation application.
When I open the Explore Data landing page, I can access the Insights without any issue. However, after spending some time working elsewhere in the application (while the user session is still active and the user is continuously performing actions), if I navigate back to the Explore Data landing page, it prompts me to log in again.
This behavior is observed only for the Explore Data landing page. Other landing pages continue to work as expected without requiring re-authentication, which indicates that the user’s Pega session is still active.
Has anyone encountered this issue before? Is there any specific session management, authentication, or configuration related to the Explore Data landing page or Insights that could cause it to require re-authentication independently of the main application session?
If the Pega session had actually expired, every landing page would redirect to the login page. Since only Explore Data is affected, this points more towards Insights authentication or a separate OAuth/token issue than a normal Pega session timeout.
Explore Data is different from standard landing pages because it relies on the Insights service and Constellation DX APIs.The application session may still be valid while the OAuth access token used by Insights has expired.
The issue is likely not a Pega session timeout, since the user remains active and other landing pages continue to work. It appears to be specific to the Explore Data/Insights functionality.
Most common causes of this:
An OAuth access token or refresh token used by Explore Data/Insights is expiring independently of the main Pega session.
Explore Data uses a separate authentication flow (DX APIs/Insights services), which may require token renewal.
A 401 Unauthorized response from the Insights APIs could be triggering the login prompt.
Recommended checks:
Verify the OAuth Client Registration, access token lifetime, refresh token lifetime, and authentication profile used by Insights.
Use the browser Network tab to check for 401, 403, or 302 responses when reopening Explore Data.
Review the browser Console, PDC, and server logs for authentication, OAuth, or DX API errors.
@NB0162481 are you in the User Experience Expert Circle? I would like to move this under that area, so it can be found with other Constellation questions. However, if you are not a member you won’t be able to respond (until you join), so don’t want to just move on you.
