{ "error": "INVALID_SESSION", "message": "Session not found", "code": 404 } - we’re seeing this intermittently when the Bot Connector attempts to hand off to the IVR on a Dialogflow CX intent fallback. It’s…odd. The session should exist, we’re passing the correct CX session ID - it’s validated in the logs before the POST to create the secure IVR session.
We’re using the latest Bot Connector SDK (Java v1.3.2) and CXone version 23.2.6. It feels like a timing issue - the session isn’t fully propagated to CXone before the connector tries to connect. In Genesys Cloud, the architecture is different, sessions are much more persistent, it’s almost a non-issue. But CXone…it’s more sensitive. It’s like a race condition between the SDK’s attempt to retrieve the session and CXone finishing the session setup.