Just noticed that the predictive routing configuration export via API returns null values for digital channel routing profiles when pulled from eu-west. The bulk export job completes successfully but the JSON manifest lacks the required channel_id mapping for legal audit trails. How do I force the inclusion of digital channel metadata in the predictive routing export payload?
This is typically caused by the default export scope excluding digital channel attributes. You need to explicitly set the includeDigitalChannelMetadata flag to true in the request body. Refer to this guide for the exact payload structure: support.genesys.cloud/articles/export-digital-metadata.
This looks like a scope limitation in the export tool rather than a config error.
- Try using the WFM scheduling API to pull agent availability instead, which often includes richer metadata.
- Check if the digital channel profiles are explicitly tagged in the routing rules before exporting.
- Verify the export job isn’t filtering by legacy voice-only parameters.