Legacy Dev Forum Posts

 View Only

Sign Up

  • 1.  Bulk Delete API failing

    Posted 06-05-2025 18:22

    Chris_Dalziel | 2022-06-27 14:54:59 UTC | #1

    I am trying to bulk delete recordings in our ORG with the API below. It works for recordings in 2020 but i have been trying to run the same API for recordings in 2021 and I keep getting the error below. I am pretty sure these calls are archived in 2021. I am not sure if there were archived in 2020.

    /api/v2/recording/jobs

    "id": "bbd7509f-a4ca-49e0-8e83-79c244111dda", "state": "FAILED", "recordingJobsQuery": { "action": "DELETE", "actionDate": "2022-06-25T05:57:02.234Z", "includeScreenRecordings": true }, "dateCreated": "2022-06-25T22:27:15.864Z", "totalConversations": 0, "totalRecordings": 0, "totalSkippedRecordings": 0, "totalFailedRecordings": 0, "totalProcessedRecordings": 0, "percentProgress": 0, "errorMessage": "{\"Error\": \"UnrecoverableException\", \"Cause\": \"{\\\"errorMessage\\\": [\\\"Analytics Query Failed {\\\\\\\"state\\\\\\\":\\\\\\\"FAILED\\\\\\\",\\\\\\\"errorMessage\\\\\\\":\\\\\\\"The executed query encountered an unexpected error\\\\\\\",\\\\\\\"submissionDate\\\\\\\":\\\\\\\"2022-06-25T22:27:16.156Z\\\\\\\"}\\\", \\\"errorType\\\": \\\"UnrecoverableException\\\", \\\"requestId\\\": \\\"805703fb-8380-4e66-b4f8-a3eee2da61c1\\\", \\\"stackTrace\\\": \\\" File [\\\\\\\"/var/task/newrelic/api/lambda_handler.py\\\\\\\", line 135, in nrlambdahandlerwrapper\\\\n result = wrapped(args, *kwargs)\\\\n\\\", \\\" File [\\\\\\\"/var/task/analyticsquerystatemachine/checkquerystatus.py\\\\\\](file://%22/var/task/analyticsquerystatemachine/checkquerystatus.py/)", line 69, in lambdahandler\\\\n raise UnrecoverableException('Analytics Query Failed %s' % response.text)\\\\n\\\"]}\"}]", "failedRecordings": "/api/v2/recording/jobs/bbd7509f-a4ca-49e0-8e83-79c244111dda/failedrecordings",

    John_Carnell | 2022-06-27 18:21:24 UTC | #2

    Hi Chris,

    The error you are having returned is an internal error and is not expected. Please open a ticket with our customer Care team. The Care team should open a ticket with the engineering team to work to get the issue resolved.

    Thanks, John Carnell Manager, Developer Engagement

    system | 2022-07-28 18:22:01 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 15313



Related Content