export-debugger
Export Debugger
Purpose
Diagnoses why a specific user was or wasn't exported to an external platform. Traces through the full export pipeline: segment membership -> job status -> flow state -> quiet windows -> export logs. Read-only diagnostic.
Environment
Requires authenticated API access. See ../references/auth.md for credential resolution.
Inputs
- User identity (field + value, e.g.,
email user@example.com) - Export destination: job ID, job name, platform name, or flow name
- Table (default:
user)
Diagnostic Flow
Step 1: Identify the Export Job
If the user provides a job ID, fetch it directly. Otherwise, find the relevant job:
More from lytics/agent-skills
entity-lookup
Look up user profiles by identity field and value. Use when the user wants to find or look up a specific user profile by email, user ID, or other identity field.
34profile-explorer
Interactive profile exploration combining lookup, segments, and event history. Use when the user wants to explore a user profile, view segment memberships, or browse event history for an identity.
33integration-setup
Guided setup for data integrations -- connection, auth, and job creation. Use when the user wants to set up, configure, or connect a new data integration end-to-end.
32audience-snapshot
Analyze what an audience looks like -- demographic breakdowns, top field values, coverage rates, and distributions. Use when the user wants to understand audience composition, view segment demographics, or analyze field coverage for a segment.
32data-health-monitor
Single-command data health check -- streams, jobs, schema, and quota status in one report. Use when the user wants to check data health, view system status, or get an overview of streams, jobs, and schema health.
32stream-inspector
Inspect data streams, view stats, and browse recent events. Use when the user wants to list streams, view stream statistics, or browse recent stream events.
31