What is the correct way to handle ServiceNow OAuth token refresh in Architect Data Actions

Architect & Flows
1

What is the standard approach to handle ServiceNow OAuth token refresh in Architect Data Actions without triggering a 401 Unauthorized error?

Background

We are running a Genesys Cloud Architect flow that triggers a ServiceNow Data Action to create incidents from digital channel conversations. The integration uses OAuth2 Client Credentials flow.

Issue

The Data Action consistently returns HTTP 401 Unauthorized when the access token expires. The flow does not automatically request a new token, causing the webhook payload to fail silently in ServiceNow.

Troubleshooting

  • Verified the client credentials are valid via Postman.
  • Confirmed the token endpoint returns a refresh_token.
  • Checked Genesys Cloud Data Action configuration; no field exists for automatic token refresh logic.