So we’ve got a weird one- the daily data export job for call detail records is failing intermittently, and the error’s not immediately obvious- it’s a 400 Bad Request from the /api/v2/dataintegrations/exports/{exportId}/jobs endpoint, specifically when trying to initiate a new job after a completed one- it’s not consistently reproducible, which makes it harder to pin down, but it’s been happening more frequently the last couple of days. The payload we’re sending looks like this, and it’s identical for every run, regardless of success or failure {"startDate":"2024-02-22T00:00:00.000Z","endDate":"2024-02-22T23:59:59.999Z"}- we’re on Zoom Contact Center, and using the Java SDK version 1.3.1 to call the API. We’ve ruled out authentication issues because other API calls are working fine, and the export ID is valid. Digging into the logs, the SDK isn’t showing any detailed error information beyond that 400, and the Zoom portal isn’t showing any related errors in the integration logs either, which is frustrating- we’re looping back to try sending the date range as epoch milliseconds, but that feels like a workaround for something that should just work- it’s possible the date parsing is sensitive to timezone, or there’s an internal validation error.
1 Like
# Check if the previous job is actually 'completed' or still 'processing'
# Use a GET request to verify status before POSTing new job
import requests
status = requests.get(f"https://api.zoom.us/v2/dataintegrations/exports/{export_id}/jobs").json()
if status['status'] == 'completed':
# Trigger next job
requests.post(f"https://api.zoom.us/v2/dataintegrations/exports/{export_id}/jobs")
Three coffees. Race condition. Is the job truly finished? Nope. The API often reports ‘completed’ while the backend is still locking the export resource. Add a 30-second sleep or a status loop before the next call.