Skip to main content

SF Plug-In deployment - 'Launch Journey Button' greyed out

This article explains why Launch Journey Button is greyed out

One of our customer has deployed the Salesforce PlugIn in their EDGE testing environment using the supplied document

The deployment appears to be successful, however they have reported that the button to launch journeys is disabled.

Root cause:

One "common" error is that the user authenticates against the incorrect fenx tenant. The tenant id configured in the custom metadata types is the fenx tenant they need to authenticate against.

Solution:

Log out fenx first in the browser.

Example: a user has access to 2 Fenx tenants. Salesforce is configured with the tenant id of tenant 1. The last time the user accessed fenx was to tenant 2. The browser remembers this in the session. When the user is going to try to do the external authentication, it will pick automatically the tenant 2 from the session, which is wrong because the user wants to connect to tenant 1 Sames happend with facebook, google, the browsers remembers the account you logged in last time

Did this answer your question?