---
id: troubleshooting.fieldloop
title: Fieldloop Intake and Processing
summary: Diagnose destination, admission, source permission, processing, and Thread gaps without resubmitting changed data or inventing findings.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-10-30
canonical: /docs/troubleshooting/fieldloop
---

# Fieldloop Intake and Processing

## Symptom

A submission has no expected log, a batch reports rejected or conflicting rows, processing is waiting, or captured records have not produced an expected Thread.

## Likely causes

- The credential, Project or source destination does not match.
- The original submitter's receipt is being read from another principal.
- A retry changed content while keeping the same idempotency identity.
- Intake is admitted but row processing is not complete.
- Source processing consent is absent or revoked.
- Provider capacity or a recorded processing failure delayed analysis.
- The selected records do not support an inquiry.

## Fix

Inspect the original receipt and its row counts first. Confirm the workspace, Project, source and original logical request. Retry an uncertain submission only with its exact content and key.

Read Logs for captured content and processing state. Check the source's current permission and the reported error through the normal controls. Keep accepted records and their provenance intact.

A missing Thread is not automatically an intake failure. Analysis may legitimately publish no inquiry. Do not invent a report, change source facts or broaden provider access to force a visible result.

If a typed input-coverage discovery was published, inspect its related Inbox item separately. Report publication, Case generation and dataset adoption have different outcomes.

## Prevention

Retain original source records until admission is known. Keep credentials in the host secret mechanism, preserve exact retry identity and monitor row outcomes rather than HTTP success alone.

Configure source permission deliberately. Revoke processing through its owning control when needed; do not treat an access change as authorization to rewrite published history.
## Related task pages

{% related-card-grid title="Related task pages" %}
- [Fieldloop](/docs/fieldloop)
- [Capture and Inspect Logs](/docs/fieldloop/ingest-logs)
- [Read Fieldloop Threads](/docs/fieldloop/threads)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [API Keys and Delegated Access](/docs/admin-console/api-keys)
- [Input Coverage Inbox](/docs/coverage-design/inbox)
{% /related-card-grid %}