Stuck on a 400 Bad Request when calling POST /api/v2/recordings/screen/interactions. The payload expects a valid interactionId, but our legacy Zendesk tickets do not map cleanly to Genesys Cloud interaction schemas.
In Zendesk, we tracked sessions via simple ticket IDs. Now, the Architect flow seems to generate ephemeral IDs that disappear before the recording upload hook triggers. This disconnect is breaking our compliance archive.
How should we bridge this gap? Are we supposed to store the interactionId in a custom attribute during the initial digital channel handshake to reuse it later?