⚡Quick answer-
When the Logs service is down, you lose only the searchable history—active calling still works.
What breaks:
• Calls → Logs page, log exports, and Log APIs stop returning new records.
• Any dashboards, reports, or alerts that rely on those logs stall or show gaps.
What keeps working:
• Live telephony (IVR, queues, recordings, billing)
• After-Call webhooks and any CRM that ingests them in real time
When to use this guide?
When you want to know exactly what breaks vs. keeps working when Logs are down, how to keep operations moving, and how to verify/backfill once restored.
What are “Logs” in MyOperator?
The Logs service powers the Calls → Logs view and related exports/APIs used to search, filter, and analyse call records (caller/callee, status, timestamps, duration, tags, recording links).
Immediate workarounds
- Use live views for operations
- Calls → Live (if available) to monitor active calls/queues.
- Rely on integrations already in place
- After-Call API/Webhook to capture CDRs directly in your CRM while Logs are unavailable.
- Pause non-critical exports
- Hold scheduled CSV/BI jobs to avoid partial data; reschedule after recovery.
- Create manual follow-ups
- If alerts depend on Logs, temporarily switch to Follow-Up rules or manual lists from your CRM/webhook feed.
Verify and backfill after recovery
- Spot-check new calls:
Calls → Logs → filter by last 60 minutes — Confirm new entries appear. - Check a known test call:
Ensure recording link, tags, and disposition are present. - Run a one-time export:
Export the outage window to CSV and reconcile with your CRM/webhook store. - Re-run integrations:
If your CRM ingest is paused, replay using the exported CSV or your webhook backlog.
Data integrity tips:
- Expect out-of-order arrival as the system catches up.
- Guard against duplicates in your BI/CRM (dedupe by call_id/UID + timestamp).
Troubleshooting (self-checks)
- Browser issue? Try an incognito window, clear cache, or a different browser.
- Scope filters too narrow? Remove all filters, then reapply by time/DID/department.
- Permissions: Confirm your role can access Calls → Logs.
- APIs: If your Log API queries time out, retry with a smaller time window.
Escalation (copy-paste template)
Subject: Logs outage/partial data — [Account ID]
To: support@myoperator.com
Body:
Account/Company: [ ]
Time window impacted (IST): [start → end]
What fails: [Search / Export / API / Reports]
Filters used (if any): [DID, dept, user, time]
Error/screenshot: [attach]
Business impact: [e.g., missed SLAs, daily report blocked]
Alternate data source in use: [Webhook/CRM/None]