fair-rose•7d ago
URGENT - Frontend Dashboard Not Displaying Call Logs
Hello VAPI Support,
I’m experiencing an issue where call logs are visible via the API but do not appear in the dashboard. Here are the details:
- Call ID: 6a96b8e7-8fb3-44bd-aabc-5259f0f080be
- Organization ID: 6c7396ee-497c-4075-8348-946295ca878a
Symptoms observed in the browser:
1. Network request to Cloudflare PAT endpoint fails with 401 Unauthorized:
GET https://challenges.cloudflare.com/cdn-cgi/challenge-platform/.../pat/... → 401 Unauthorized
2. Sentry logging is rate-limited:
POST https://o4506313494298624.ingest.us.sentry.io/... → 429 Too Many Requests
3. Console warnings indicate failed fingerprint integrations:
Dodgeball SDK: No URL provided for integration: DODGEBALL_FINGERPRINT_SERVICE_V2
What I’ve confirmed:
- The API calls to /call/list and /call/{id}/logs succeed and return the expected call data.
- This indicates the backend and recording settings are functioning correctly.
- The issue appears to be frontend-related, likely related to the Cloudflare PAT mechanism or dashboard JS failing to load required resources.
Request:
Please advise on:
1. How to ensure the dashboard frontend properly retrieves the private access token for my account.
2. Any additional steps needed to fix the call log rendering issue for this Call ID.
Thank you for your assistance.
Best regards,
Felix
1 Reply
Hi there,
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team Hey! To help track down this issue, could you share: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
Vapi
Customer Support Team Hey! To help track down this issue, could you share: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!