Downloads recording information for conversations.
This action populates the recording_info table with recording information.
Any recordings that return with status code 403 (Not authorised) or 404 (Not found) will instead be stored in failed_recording_info table.
This action requires that conversations have been downloaded already, using either the conversations() or the conversations_from_datalake() action.
The action will download recordings for all matching conversations that span the start and end dates.
A conversation spans the dates if any part of the conversation occurs between the start and end dates.
The max_concurrent_downloads setting can be set higher to download very large amounts of recording information.
The retry_failed parameter can be set to true to only re-attempt recordings that previously failed to download, due to permissions or archiving. This can be useful if the CX Vizz credentials in Genesys have had additional permissions added since the last run.
As this action can potentially take a very long time to run, it provides an ETA every second in the log file.
Parameters
| Parameter | Description | |
|---|---|---|
| start_date | Required | defines the start of the download range |
| end_date | Required | defines the end of the download range |
| division_id | Optional | restricts recording info to only conversations in the specified division id |
| media_type | Optional | restricts recording info to only conversations with the specified media type |
| max_concurrent_downloads | Optional | The maximum number of concurrent downloads to run. Defaults to a value stored in configuration as 'MAX_CONCURRENT_DOWNLOADS', or 20 if no configuration is set. |
| retry_failed | Optional | true or false (false if not specified). If true, this action will only re-attempt recordings (those in the failed_recordings table) that previously failed to download, due to permissions or archiving |
Tables Affected
Variables Set
No variables set.
Permissions needed
- recording:recording:view or recording:recordingSegment:view
Examples
- recording_info( start_date='2024-01-01', end_date='2024-01-31' + 1 day, max_concurrent_downloads=80 )
- recording_info( start_date='2022-01-01', end_date='2024-01-01', retry_failed=true, max_concurrent_downloads=20 )