Verify Data Flow

After setup, confirm telemetry data is reaching Flowstate.

Check Configuration Status

See which tools are detected and configured:

flowstate-telemetry status

Example output:

Tool               Detected   Configured   Prompts
────────────────────────────────────────────────────
claude-code        ✓          ✓            ✗
copilot-chat       ✓          ✗            –
cursor             ✓          ✓            –

Verify Configuration

Check that your telemetry configuration is correct for all detected tools:

flowstate-telemetry verify

This checks each tool for proper endpoint and key configuration and reports warnings if --prompts wasn't used during install.

Check the Dashboard

1. Open Flowstate and navigate to AI Workforce
2. Your sessions should appear within 60 seconds of your first AI interaction

TIP

There is a 60-second flush delay before session data appears. The telemetry service buffers events and aggregates them into sessions before forwarding to Flowstate.

Test With a Quick Prompt

Use your configured AI tool to make a simple request:

# Example with Claude Code
claude "What is 2 + 2?"

Wait 60 seconds, then check the AI Workforce dashboard for the new session.

Common Issues

Symptom	Cause	Fix
No sessions appearing	Tool not configured	Run flowstate-telemetry install --all
"Invalid key" error	Legacy ak_ key format	Generate a new key from Profile → AI Telemetry
Sessions delayed > 2 minutes	Network/firewall blocking OTel	Check outbound HTTPS to otel.flowstate.inc
Sessions appear but no cost data	Model not in pricing table	Costs update as pricing data is added for new models
Wrong user attribution	Key shared between engineers	Each engineer must use their own telemetry key
"Key verification failed"	Key revoked or org mismatch	Generate a new key from Profile → AI Telemetry

Next Steps

• Tool-specific guides for manual configuration and troubleshooting