Testing and Reconnecting

Testing and Reconnecting

Use Test Connection to verify that the connector can reach your Salesforce org at any time. If the OAuth token has expired or the Connected App credentials changed, use Reconnect to refresh the token without re-entering credentials.

Testing a Connection

  1. In the Connections tab, find the connection you want to test.

  2. Click the Test button (or Test Connection in the connection detail).

  3. The connector calls the Salesforce REST API (/services/data/v58.0/) and reports success or the specific error.

Connection test button with success confirmation

Test Connection button and success result message

A successful test confirms:

  • The Login URL is reachable from Forge's servers

  • The stored access token is valid

  • The Connected App has API access

Reconnecting After Token Expiry

The connector auto-refreshes access tokens in the background using the stored Client Credentials. If the token cannot be refreshed automatically — for example, if the Connected App was modified or revoked — the connection status changes to Expired.

To reconnect:

  1. In the Connections tab, click the connection showing Expired status.

  2. Click Reconnect. The connector uses the stored Client ID and Client Secret to request a fresh token from Salesforce.

  3. If reconnection succeeds, status returns to Authorized.

Connection row showing Expired status with Reconnect button

Expired connection with Reconnect button highlighted

If Reconnect Fails

If reconnect fails, the stored credentials may no longer be valid. This happens when:

  • The Client Secret was rotated in Salesforce

  • The Connected App was deleted or disabled

  • The "Run As" user no longer has API access

In this case, delete the connection and create a new one with updated credentials.