Runtime Issues

Use the following common troubleshooting steps to resolve any runtime issues with the Payments Agent.

Issue	Likely Cause	Resolution
“Sorry, the details you requested are currently unavailable” appears when accessing Payment Agent	Missing permission groups or a backend API timeout.	For 403, enable permission groups for Payment Specialist. Log an SR with Oracle Support, for 504, retry and collect HAR, network logs, and console logs if the issue persists.
Payment Agent redirects to an access requirement page	Read-optimized data store isn’t enabled for the environment.	Raise a service request to enable read-optimized data store, then re-login and confirm Payment Agent opens normally.
Payment Agent can’t access specific Business Unit-linked information	Business Unit data access is missing.	Add the required BU access, run the job, then confirm the BU appears in the filter and linked information is returned.
Payment Agent returns empty results for a Business Unit after BU access is assigned	The BU access was added, but the data access layer wasn’t synchronized.	Run Process Permission Group Policies, re-login, and confirm Payment Agent returns data for the authorized BU.
Agent returns the same table when asked to add more details or columns after analysis	This is expected structured-output behavior.	Ask for the additional information as a separate question instead of requesting the table structure to change.