Introduction
When you connect a storage and start a sync, RecordsKeeper.AI creates a batch. Each batch discovers files, applies your filters (type, size, name), processes what qualifies, and records outcomes for every file.
Sync Batches & Logs is the command center for all of that: it lists your batches, lets you open any batch for details, and shows file-level logs and reasons for failures so you can take action.
Main Content
1) Navigate the Sync Batches & Logs list
What you’ll see
Batch # – Auto-incremented run number.
Batch ID – Unique identifier (click the copy icon for audits/support).
Source Name – The storage/folder synced (e.g., “Sales Invoices”).
Total Files – Discovered files for this run.
Created On / Last Updated On – Start time and the latest activity.
Status – Current state (e.g., Active, Synced, Failed).
Action → View Logs – Opens the batch details page.
How to work the page
Use the Search bar to find a batch by name or ID.
Click a column header to sort (helpful for seeing the newest or most active runs).
Use Filter (if available) to narrow by status or date.
Click View Logs to drill into a single batch.
2) Understand a batch at a glance (Batch Details header)
The top card explains who, when, and how the batch ran, plus usage:
Connected By / Connected On - Who authorized the storage and when.
Source ID - Identifier for the specific connection used.
Sync Type -
Initial - process all eligible files.
Incremental - only new/changed files since the last success.
Status Reason - Why the batch is in its current state (plain English).
Resumable - Whether this run can continue from where it stopped.
Timing & usage
Batch Started At / Completed At - The window of the run.
Batch Created On / Last Updated At - Record creation and latest change.
Storage Credit Consumed - Storage used by files actually ingested.
Credits Consumed (File Processing Credits) - AI work done (OCR/classification/extraction).
3) Read the batch counters (what each number means)
Files Available - Discovered items that match your inclusion policies; upper bound of what could be processed.
Queued Files - Eligible files waiting for a worker; expect this to drop during an active run.
Skipped Files - Intentionally not processed (policy rules, duplicates, unsupported types).
Qualified Files - Passed basic checks (type/size/policy). Roughly Processed + still Queued.
Processed Files - Work actually attempted - Synced + Failed.
Classified Files - Processed files the AI understood (type detected, metadata extracted).
Synced Files - Fully processed and stored; ready for search/workflows.
Failed Files - Didn’t complete; click into logs to see why.
Quick reads
Big Skipped? Check your rules/filters.
High Failed? Open logs and inspect reasons.
Surprising Credits Consumed? You likely processed large PDFs/images or many pages.
4) Investigate file-level results (Sync Logs)
The logs list each file with:
Name & size
Processed time
Status badge - Synced (success) or Failed (error reason shown, e.g., Password Protected)
Row actions (⋯) - Options such as viewing details or retrying (when available)
Use the Search box to quickly find specific filenames, types, or statuses.
5) Use the file details side panel
Click a file row to open the panel on the right:
File Sync Status and Status/Failure Reason – Current state and the clearest explanation available.
File ID (copyable), File Size, Synced At, Created/Updated At (from source), File Mime Type.
Credits Consumed – File-level AI credits.
Storage Consumed – Space used by this file.
Sub Status – Extra context when applicable (e.g., “scan pending”).
Fixing common failures
Password Protected → remove password and retry.
Unsupported/Corrupted → replace with a supported/healthy copy.
Permission/Network → repair source access and rerun.
Conclusion
Sync Batches & Logs gives you clear visibility from the batch level down to individual files. Start at the list to spot activity and status, open Batch Details to understand scale and usage, and use Sync Logs + the file panel to resolve issues quickly. With a quick review of counters and reasons, plus targeted filters for future runs, you’ll keep your data tidy, costs predictable, and syncs running smoothly.