Data Ingestion Queue — Monitor, Pause, Resume, Retry and Manage Your Ingestion Jobs
Ingestion Queue Management
Every document you submit through the Data Ingestion API goes into a processing queue. The Ingestion Queue page in your account gives you full control: monitor progress in real time, pause jobs mid-processing, resume them later, retry failed or completed jobs, edit payloads to fix errors, or delete jobs you no longer need. Only indexes with active or recent jobs appear — no clutter.
How to Access
Or navigate directly to /admin/solr_manager/my_ingestion_queue
What You See
Grouped by Index
Jobs are grouped by index name. Only indexes that have jobs in the queue are shown — if an index has no pending or recent jobs, it won’t appear.
Live Progress
Each job shows a progress bar with the count of processed, successful, and failed documents. The page auto-refreshes every 10 seconds while jobs are processing.
Pause & Resume
Pause a job mid-processing. It remembers where it left off and resumes from the exact same document when you continue.
Retry Jobs
Re-run completed, failed, or stopped jobs from scratch. Retry resets progress to zero and re-processes every document in the payload.
Edit Payload
Fix errors directly in the queue. Click any failed, stopped, or paused job to open its detail view, edit the JSON payload in place, save it, then retry. No need to re-submit via the API.
Error Details
Failed jobs show the error message. Completed jobs with partial failures show per-document success and error counts.
Queue Interface
Job States
Pending
Waiting in queue
Processing
Enriching & indexing
Completed
All docs processed
Paused
User paused
Stopped
User cancelled
Failed
Error occurred
Available Actions
| Action | Available When | What It Does |
|---|---|---|
| Pause | Pending, Processing | Pauses the job. Processing stops at the current document. Progress is preserved. |
| Resume | Paused, Stopped | Re-queues the job. Processing picks up from where it left off. |
| Stop / Cancel | Pending, Processing | Stops the job permanently. Documents already indexed remain in the index. |
| Retry | Completed, Failed, Stopped | Resets the job back to Pending and clears all progress counters. The entire payload is re-processed from scratch. Useful after fixing errors in the payload or when you want to re-index all documents. |
| Edit Payload | Failed, Stopped, Paused | Opens the job detail view where you can directly edit the JSON payload in a full-size editor. Fix field names, correct values, add or remove documents — then save and retry. |
| Delete | Any state | Removes the job from the queue. Does not remove already-indexed documents from Solr. |
Edit Payload & Retry Workflow
When an ingestion job fails — bad field names, malformed data, missing required fields — you don’t have to re-submit the entire request through the API. You can fix the problem directly in the queue:
Fix & Retry in 3 Steps
job row
payload & Save
with fixed data
uri fields and updates the total document count.API Queue Management
You can also manage the queue programmatically:
| Endpoint | Purpose |
|---|---|
GET /api/ingest_status?job_id=... | Check progress of a specific job |
GET /api/ingest_queue?core_name=... | List all jobs for a core |
POST /api/ingest_queue_action | Send job_id + queue_action. Available actions: pause, resume, stop, delete, retry, save_payload |
For the save_payload action, include a payload parameter with the full JSON array of documents. The system validates it, regenerates document IDs from uri fields, and updates the total document count automatically.
All API endpoints require email and api_key authentication. You can only see and manage your own jobs.
Ready to push documents into your index? Check out the full API reference.
API Documentation