What’s the best way to handle OAuth token expiration for ServiceNow integrations when using Genesys Cloud Data Actions for automated incident creation? We are currently deploying a security-compliant workflow where Genesys Cloud acts as the trigger for creating incidents in ServiceNow based on specific digital channel conversation tags. The setup utilizes a Data Action configured with HTTPS POST to the now.com/api/now/table/incident endpoint. Initially, the integration functions perfectly, successfully creating records with the correct payload structure, including caller ID, short description, and custom fields mapped from the Genesys conversation context. However, after approximately 3600 seconds, which aligns with the default OAuth2 access token lifetime in our ServiceNow instance, the Data Action begins returning a 403 Forbidden error with the message “Invalid access token”. The current configuration does not support automatic token refresh within the Data Action node itself, causing the entire Architect flow to fail at the Data Action step without falling back to a retry mechanism or a token refresh sub-flow. We have reviewed the Genesys Cloud documentation on secure integration patterns, but it is unclear whether the recommended approach involves implementing a separate middleware service to manage token lifecycle or if there is a native capability within Genesys Data Actions or Webhooks to handle OAuth2 refresh tokens seamlessly. The environment is Genesys Cloud EU (v23.11) and ServiceNow Washington DC (v13.3). The error logs in Genesys show the request failing at the HTTP level before any response payload is processed, indicating the authentication handshake is rejected by ServiceNow. This issue is blocking our compliance audit as we cannot guarantee uninterrupted logging of customer interactions to the ticketing system. We need a robust, automated solution that ensures the Data Action always uses a valid access token without manual intervention or flow interruption. Is there a supported pattern for integrating OAuth2 refresh logic directly within the Genesys Cloud Architect flow or Data Action configuration to prevent these 403 errors during peak load times?