Stuck on the /v2/screensharing/recordings endpoint returning a 400 with "message":"Invalid recording ID format". In Zendesk, ticket attachments were just simple S3 links, but here the recordingId seems to require a specific UUID structure that the migration script isn’t catching. Any hints on how to validate the ID format before the call?