Skip to main content
Use this page when connecting Genesys Cloud fails, a setup step stops, or a setting can’t be switched on. Each entry gives the likely cause and the fix. For other problems, start at Troubleshooting.

”Genesys rejected these credentials. Check the client ID, secret and region.”

: wrong client ID, secret or region. Fix: copy both values again from Admin → Integrations → OAuth, confirm the grant type is Client Credentials, and check the region.

”This Genesys organization is already connected to another OpenCX workspace”

: another workspace uses this organization. Fix: disconnect it there first, then connect here.

Signing in with Genesys returns an error

: the admin lacks permissions, or the region is wrong. Fix: follow the message shown. The Genesys admin is missing permissions names what’s missing, so sign in as an admin who has it. That Genesys organization is in another region means you should pick the region from your Genesys address.

Genesys shows its own error page after Connect Genesys

: your org enforces OAuth scopes and this admin can’t approve new applications. Fix: sign in as an admin with oauth:client:authorize, or connect with a client ID and secret.

A setup step shows failed or action required

: the step is waiting for you, or Genesys returned an error. Fix: read what the row says and use the button beside it. See Finish setup.

Go live or a setting is greyed out

: something it needs isn’t there yet. Fix:
  • Go live: the text beside the button names what’s missing: Genesys connection on is off, the connection needs reconnecting, or the checklist’s routing or flow step isn’t done.
  • Show every Genesys conversation, native email and messaging, live phone assist and AI on calls: go live first.
  • Smart routing: set Handoff routing to Let my Genesys flow decide.
  • Create a workitem, On handoff and Email sessions: choose a Worktype first.
  • AI answers after wrap-up: set When a Genesys conversation ends to Close the session.
  • Everything: you need the Manage integrations permission to change Genesys Cloud settings.

OpenCX can’t see your users or queues

: they’re in a division the role isn’t granted in. Fix: if you connected by signing in, click Reconnect and choose that division too. With a client ID and secret, grant the role there in Genesys and compare it with Permissions.

Routing asks you to choose a queue again

: the default queue is outside the divisions the connection can see. Fix: choose a queue beside Routing, or add its division.

Reconnect says oauth:client:edit is missing

: the admin changed the divisions but can’t edit OAuth clients. The connection keeps the divisions it had. Fix: sign in as an admin with oauth:client:edit, or keep the current divisions.

The Knowledge import asks for permissions

: the role can’t read Genesys Knowledge. Fix: add knowledge:knowledgebase:view and knowledge:document:view to the role OpenCX uses, then click Import again.

The past conversations import asks for permissions

: the role can’t read conversation analytics, or the transcripts Genesys keeps for ended messaging conversations. Without the second, emails import and messaging is skipped. Fix: add analytics:conversationDetail:view and recording:recording:view to the role OpenCX uses, then click Resume beside Past conversations.

Health shows an Erasure warning

It shows while Delete contacts in Genesys too or Apply Genesys deletion requests is on, and whenever an erased session’s Genesys copy is waiting or wasn’t cleared. See Erasure.
  • Erasures waiting for the connection: sessions were erased while Genesys connection on was off or the connection needed reconnecting. Fix: turn the connection back on or reconnect. They reach Genesys within a minute.
  • Erasures not cleared in Genesys: they waited 6 days, or Genesys was disconnected or connected to another Genesys organization before they could run. The audit log lists each one. Fix: clear the OpenCX data on those conversations and contacts in Genesys by hand. The count clears after 30 days.
  • Permission missing: Genesys refused to read or file a deletion request. Fix: reconnect Genesys with an admin who holds gdpr:request:view and gdpr:request:add, or add them to the role OpenCX uses. A refused request isn’t filed again, so file it in Genesys yourself. The warning clears within a day.
  • Too many deletion requests to read: more deletion requests were filed in Genesys since OpenCX last applied one than it reads at once, so none are applied. Fix: contact OpenCX support.
  • Deletion requests matched several contacts: OpenCX skipped them rather than guess. Fix: find who each request was about, then erase that person’s sessions by hand. The count clears after 30 days.
  • Deletion requests matched no contact: no contact Genesys knows has the request’s external contact, email or phone number, so OpenCX erased nothing for them. Fix: find who each request was about, and erase any sessions they have in OpenCX by hand. The count clears after 30 days.

Connect Genesys Cloud

Sign-in, client credentials, setup and regions.

Permissions

Everything the role OpenCX uses can hold.