Troubleshooting

Common issues and how to fix them. If your problem is not listed here, check the error codes reference.

*
Quick Debug Checklist
  1. Check the cell status badge, click it for error details
  2. Check the column run progress bar, expand error list
  3. Verify your AI provider key in Settings > AI Providers
  4. Check the audit log in Settings for recent errors

Smart Column Issues

My smart column is not running

Smart columns only execute when triggered. Check these common causes:

How to fix:

1. Verify you have an AI provider key saved (Settings > AI Providers) 2. Check that the column has auto_run enabled, or trigger it manually with the Run button 3. Check the run_condition, if set, rows must match the condition 4. Look at the column run progress for error details

Cells show "Error" status

Click the cell to open the Cell Details panel. The error message tells you exactly what went wrong. Common causes:

How to fix:

1. Invalid or expired API key, check Settings > AI Providers 2. Rate limit exceeded, reduce the rate_limit preset or wait 3. Prompt too long or invalid, simplify the prompt template 4. Target API unreachable, check the URL in HTTP column config 5. Circuit breaker tripped, >50% error rate pauses the column. Fix the root cause, then retry.

Column says "circuit breaker tripped"

The circuit breaker activates when more than 50% of cells fail within 60 seconds. This protects your API budget.

How to fix:

1. Check the error messages on failed cells (click any red cell) 2. Fix the root cause (usually: wrong API key, bad URL, or malformed prompt) 3. Go to the column settings and click "Retry Failed Cells" 4. The circuit breaker resets automatically when the error rate drops below 50%

Smart column shows "unknown reference" error

Template references like {{column_name}} must match an existing column name exactly.

How to fix:

1. Check for typos, the error includes a "did you mean?" suggestion 2. Column names are lowercase with underscores: {{company_name}} not {{Company Name}} 3. For nested JSON access, use dot notation: {{research.industry}} 4. If you renamed a column, update all template refs that reference it

Data & Limits

I hit my row limit

Each plan has a per-tab row limit. When you reach it, inserts are rejected.

How to fix:

1. Delete rows you no longer need (they soft-delete for 30 days) 2. Export data to CSV before deleting 3. Upgrade your plan in Settings > Billing for higher limits 4. Use the dedupe feature to remove duplicate rows

DAG run says "rows deferred"

The DAG engine processes a maximum of 500 rows per invocation to stay within CPU limits.

How to fix:

1. This is normal for large tables, call run_dag again to process the next batch 2. The response includes deferred_count telling you how many rows remain 3. For 50K+ row backfills, run the DAG in a loop until deferred_count is 0

Connectivity

Incoming webhook is not creating rows

Check these common issues:

How to fix:

1. Verify the webhook URL is correct (GET /api/tables/:id/webhooks to see the URL) 2. Check the webhook secret matches what the sender is using 3. Payload must be a JSON object (not array, not string) 4. Check webhook logs: GET /api/tables/:id/webhooks/:id/logs

Real-time updates stopped working

WebSocket connections can drop due to network changes or token expiry.

How to fix:

1. Refresh the page, the connection reconnects with the current token and resolved table ID on mount 2. Check that your session has not expired (you may need to log in again) 3. If using an API key, verify it has not been revoked

The table page freezes when I click Add column, Integration, or Auto-run

This usually means the browser is running stale table assets or the page is still attached to a previous import-heavy session.

How to fix:

1. Hard refresh the page (Cmd+Shift+R / Ctrl+Shift+R) so the latest table UI code loads 2. Re-open the table after any large CSV import finishes; repeated uploads can keep the table busy until the import job completes 3. If only one table is affected, refresh that table route to re-establish realtime for the current table ID 4. If schema changes still work through MCP/API while the page feels stuck, the issue is in the browser session rather than the backend mutation path

Getting Help

If you cannot resolve your issue with the steps above:

  • Email [email protected] with your error code and trace ID (shown in error responses)
  • Include the column run ID if the issue is with a smart column
  • Check the Error Codes page for the full list of error codes and their meanings