Skip to main content

​
Introduction

Ensuring your Agentforce Context Protocol (ACP) server connections are active and healthy is crucial for the reliable operation of your ACP tools and integrations. The ACP Management UI provides a dedicated interface to view the status of each configured connection and test its health. This guide explains how to access this information and understand what the different statuses mean.

​
Prerequisites

  • Access to the ACP Manager Lightning App in Salesforce.
  • ACP connections configured in your Salesforce org.

​
Accessing Connection Statuses

  1. Navigate to the ACP Manager App:
    • Open the App Launcher in Salesforce (the 3x3 grid icon).
    • Search for “ACP Manager” and select it.
  2. Go to the “Connections” Tab:
    • Within the ACP Manager app, click on the Connections tab. This tab displays a list of all configured ACP server connections.
    ACP Manager Connections Tab (Placeholder: Screenshot of the ACP Manager UI, Connections tab, showing a list of connections)

​
Understanding the Connection List

The “Connections” tab will typically display the following information for each connection:
  • Connection Name: The user-defined name for the connection (e.g., “Slack Workspace Prod”, “Jira Cloud Instance”).
  • Server Type: The type of server the connection is for (e.g., slack, jira, salesforce).
  • Status: The current health status of the connection. This is often determined by a recent test or a periodic health check. Common statuses might include:
    • Active/Connected: The connection has been successfully tested and is ready to use.
    • Inactive/Disabled: The connection is intentionally disabled (e.g., via an “Is Active” checkbox in its configuration).
    • Error/Failed: The last attempt to test the connection failed. Details of the error might be available.
    • Unknown/Not Tested: The connection status has not yet been determined or tested.
  • Last Tested Date: When the connection was last successfully tested.
  • Actions: Typically includes a button or option to Test Connection.

​
Testing a Connection

The ACP Management UI allows you to manually test a connection:
  1. Locate the Connection: Find the connection you want to test in the list on the “Connections” tab.
  2. Click “Test Connection”: There should be a button or action associated with each connection (e.g., in a row-level action menu or a dedicated column). Clicking this will initiate a health check.
    • The ACP system will attempt to communicate with the configured external server (e.g., make a simple API call to verify credentials and connectivity).
  3. Observe the Result:
    • The Status field for the connection should update based on the test outcome.
    • You will typically receive a toast notification indicating success or failure.
    • If the test fails, look for error details. These might be displayed in a modal, a toast message, or logged in the Activity Log.
    Test Connection Action (Placeholder: Screenshot showing a “Test Connection” button and a success/failure notification)

​
Interpreting Connection Health

  • Active/Connected: Your ACP tools relying on this connection should function correctly.
  • Error/Failed:
    • Check Credentials: Ensure API keys, tokens, usernames/passwords are correct and haven’t expired.
    • Verify Endpoint URLs: Confirm the server URL is accurate and accessible from Salesforce.
    • Network Issues: Check for any firewall restrictions or network outages that might prevent Salesforce from reaching the external server.
    • Permissions: The credentials used might lack the necessary permissions on the external system.
    • Review Activity Log: The ACP Activity Log might contain more detailed error messages related to failed connection attempts.
  • Inactive/Disabled: If you expect the connection to be working, ensure it’s marked as active in its configuration settings (often managed via Custom Metadata Types or a specific settings area in the ACP Manager).

​
Troubleshooting Connection Issues

  1. Re-test the Connection: Sometimes, transient network issues can cause temporary failures.
  2. Verify Configuration: Double-check all connection parameters (URL, credentials, authentication type) in the ACP connection setup.
  3. Check External Service Status: The external service itself (e.g., Slack, Jira) might be experiencing an outage. Check their official status pages.
  4. Examine ACP Activity Log: The Activity Log (covered in the “Monitoring ACP Activity” guide) can provide valuable insights into what operations were attempted and what errors occurred.
  5. Consult Salesforce Debug Logs: For more in-depth troubleshooting, especially if the error seems to originate from Apex code, enable debug logs for the user performing the test or for the Automated Process user.
Regularly monitoring your ACP connection statuses ensures that your integrations remain healthy and your automated processes run smoothly.
⌘I