Stuck on a 422 Unprocessable Entity error when attempting to synchronize Genesys Cloud WEM shift templates with ServiceNow SPM schedules via a custom Data Action webhook. The environment is Genesys Cloud UK East, utilizing the latest WEM API endpoints. The flow triggers on shift template creation, formatting the payload to match the ServiceNow cmn_schedule table schema. While the initial authentication succeeds, the POST request to the ServiceNow REST API fails specifically on the periods array serialization. The error response indicates a mismatch in the time zone offset format, expecting UTC+00:00 but receiving GMT+00:00 from the Genesys side. Cross-referencing the Genesys WEM documentation, the time zone handling appears consistent, yet the ServiceNow Tokyo Release expects a strict ISO 8601 offset. The webhook payload includes start_time, end_time, and timezone, but the transformation in the Data Action seems to strip the colon from the offset. Is there a known issue with the Genesys Data Action time zone formatting for WEM entities, or should a custom script be implemented to reformat the offset before the HTTP call?