Actor Run Dataset Reconciler
Compare declared actor runs and item counts with supplied dataset/item identities, exposing shared datasets, duplicate IDs, orphan items and unsuccessful runs.
Loading tool…
How to use Actor Run Dataset Reconciler
A succeeded run label does not establish a complete dataset handoff. Compare the run metadata with the exported item inventory and keep ambiguous run attribution visible.
- Enter authorized run metadata and the item-ID inventory from the corresponding dataset export.
- Inspect physical row counts, distinct IDs, shared-dataset attribution and orphan items.
- Verify the actual actor logs and dataset before delivering results; no actor or API runs here.
Good to know
- This is run/dataset metadata reconciliation, distinct from pagination checking or marketplace payout accounting.
- A header-only item export proves only zero supplied rows. Shared datasets cannot be attributed to one run, and succeeded labels remain unverified.
- Each input field is limited to 8,000 UTF-16 characters and each exact-header CSV to 100 data rows. Quoted commas/newlines and doubled quotes are supported. Unsupported controls and unpaired surrogates are refused. Decimal magnitudes are at most 999,999,999 with a smallest nonzero magnitude of 0.000000001; exponents are refused and whole counts are checked exactly. Rational results show at most 18 fractional digits and an ellipsis when more remain.
- Editable Markdown and long-form CSV both retain all summary metrics, context, detailed findings, entered source rows and scope limitations. CSV columns are Record type,Section,Source row,Field,Value; spreadsheet-looking text is apostrophe-prefixed. These are review artifacts, not proof of source truth or a completed real-world task.
- Runs deterministically in this browser. No AI, API, vendor connection, upload, outreach, calendar change, payment, storage or background monitoring. Use authorized pseudonymous records; inspect exports before sharing.
Explore a related business case
These cases explain the business mechanism. The workbench is ToolJovia's independent adaptation, not a claim about the company's internal workflow or an endorsement.
Common questions
Why show physical rows and distinct IDs?
Repeated IDs can inflate a physical export count. Both remain visible; the tool does not silently deduplicate or infer which source row is correct.
Does a successful label prove an actor produced good data?
No. Metadata, record quality, source permissions and actual remote completeness require separate inspection.
Keep going with related tools
All data →Crawl Pagination Audit
Walk an entered cursor chain and compare page counts with item IDs to flag missing pages, cycles, duplicates and unsupported termination claims.
DataActor Earnings and Payout Ledger
Reconcile entered actor statement charges, refunds, costs, approval states and actual settlements while separating unknown balances from received cash.
DataMonitor Observation Gap Ledger
Match timestamped changed/unchanged/failed observations to a declared polling schedule and expose missing slots, duplicates and off-schedule records.