Troubleshooting EPM Assistants Issues

Implementing Oracle Fusion Cloud EPM and Oracle Fusion Cloud Enterprise Data Management EPM Assistants require you to follow a sequence of steps to achieve integration with Fusion AI Studio.

Step-by-step instructions to correctly configure Cloud EPM and Cloud EDM EPM Assistants are available in Implementing EPM Assistants in Getting Started Guide for Administrators. Use the following table to identify common configuration and validation issues with EPM Assistants.

Table 4-1 Troubleshooting EPM Assistants

Symptom What to Check First
You cannot open AI Agent Studio Fusion roles, duty roles, permission groups, profile options, and security import jobs.
You can authenticate but cannot access Oracle Fusion Cloud Enterprise Performance Management or Cloud EDM User existence in the target Cloud EPM or Cloud EDM identity domain, assigned application roles, and business process security.
SSO loops or redirects incorrectly SAML metadata, certificates, IdP and SP configuration, application assignment, IdP activation, and identity provider policy.
AI Agent Studio cannot authenticate to Cloud EPM or Cloud EDM Client ID, OAuth scope, public certificate, private key, JWT assertion, trusted client configuration, authorized resources, and application activation.
Imported business objects do not resolve to the data source Ensure that the AI Studio data Source application name matches the EPM Assistant package naming convention. For example, if the package name is EPM_AI_Agent_Artifacts-VISION_EPM1.zip the data source application name must be VISION_EPM1. See Establishing a Data Source Connection in AI Agent Studio
AI agent returns plausible but unsupported values Prompt instructions that require retrieved Cloud EPM or Cloud EDM data, visible POV or source context, and explicit responses when requested data is unavailable.

What to Do if You Get the Sorry, the assistant is unavailable right now Message

Note:

Unless otherwise noted, all references in this section are to the Implementing EPM Assistants in AI Agent Studio chapter in the Getting Started Guide for Administrators.

The Sorry, the assistant is unavailable right now message and its variants are used to indicate the following configuration issues.

  • You used a public key instead of a public certificate in the AI Agent data source configuration .

    Notes: Use the same public certificate in both the Cloud EPM or Cloud EDM trusted application and the AI Agent Studio data source application. Also, provide the matching private key in the data source application.

  • You did not use a matching pair of certificate and private key files (for example, PEM X.509 public certificate and PEM unencrypted PKCS#8 RSA private key) while configuring the AI Studio data source application.

    Ensure that the private key you use is:

    • Not encrypted
    • In PKCS#8 format.

      Note:

      If the certificate and key are in a PKCS#12/PFX bundle, use OpenSSL commands to generate PKCS#8 formatted key for use while configuring the data source application.

      Supply only the certificate and private key PEM blocks. Do not provide other blocks.

  • The secondary audience is not configured in the OAuth configuration of Cloud EPM or Cloud EDM service. See Configuring the Secondary Audience.
  • The trusted application is created in the Fusion Application's identity domain instead of the identity domain associated with Cloud EPM or Cloud EDM. See Configuring Authentication
  • You are using an incorrect base URL in the AI Studio data source application. The base URL is the first part of your service URL, without the context. Ensure that the Base URL you use doesn't contain contexts such as /Hyperion Planning, /epmcloud, and /interop

    If your service URL is https://epm-acme.epm.us-phoenix-1.ocs.oraclecloud.com/epmcloud, your <BASE-URL> is https://epm-acme.epm.us-phoenix-1.ocs.oraclecloud.com.

  • You are using an incorrect IDCS URL in the AI Studio data source application. Use the base URL of IDCS. This base URL should not contain endpoints (for example, OAuth token endpoints) such as /oauth2/v1/token, and oauth2/v1/login. See Establishing a Data Source Connection in AI Agent Studio.
  • You are using an incorrect OAuth Client ID in the AI Studio data source application. Verify that you are using the oAuth Client ID of the trusted application you configured for Cloud EPM or Cloud EDM.
  • The AI Studio data Source application name does not match the EPM Assistant package naming convention. In the Fusion AI Studio data source application, values of OAuth Scope, OAuth client id, and URL are case-sensitive and must exactly match the trusted application and EPM configuration. For example, if the package name is EPM_AI_Agent_Artifacts-VISION_EPM1.zip the data source application name must be VISION_EPM1. See Establishing a Data Source Connection in AI Agent Studio.
  • You imported EPM Assistant artifacts before creating the required data source in the AI Studio.

Other Common Issues

  • Some users are not able to access the EPM Assistant.

    This is usually caused by incorrect access privileges. See Configuring User Access.

  • Connection from AI Studio to Cloud EPM or Cloud EDM does not work although they use the same identity domain as AI Studio.

    Even in cases where AI Studio and Cloud EPM or Cloud EDM share an identity domain, you must configure the confidential application as explained in Configuring Authentication.

Getting Help

Before approaching Oracle Support for assistance, complete the troubleshooting steps available in this topic to diagnose and fix the issue. If the issue is still not resolved:

  1. Create a an HTTP Archive (HAR) file containing network trace of your session while performing the activity that results in the issue. See these topics:
  2. Create a Provide Feedback submission from the environment that has the issue.

    Optionally, allow Oracle to access the maintenance snapshot of the environment by consenting to application snapshot submission. See Creating a Provide Feedback Submission.

  3. Submit a technical service request that identifies the Provide Feedback reference number. See Submitting a Technical Service Request. The service request must contain the following additional information:
    • The HAR file containing network trace information.
    • Detailed steps to reproduce the issue.
    • Any recent changes made to the workflow or supervisor agent.
    • Whether this issue started after the EPM AI Assistant delivered in the last Cloud EPM monthly update.
    • Whether the issue started after applying the last Fusion quarterly release or patch.
    • Whether this is a critical outage.