Skip to main content
A run that fails or returns empty usually leaves evidence — the result status, the support logs, or the source data itself. The failure is fixable. Start with the result row, then work down through these checks.

​
Failed run

Check:
  • Open Ask Darpan, search by the run name or output file name, and select Open Result: ….
  • Source inputs were present.
  • Schema or RuleSet selection was valid.
  • Connection records were reachable.
  • The run or support logs show the first processing error, not only the final failure.

​
Zero matches

If zero matches followed a file upload issue — encoding, leading zeros, or delimiter — check File upload first. Check:
  • Join keys are populated in both sources.
  • Identifiers use the same formatting.
  • The selected schema reads the intended columns.
  • The files are from the same business period.

​
Unexpected differences

Classify each difference before changing configuration:
  • Source data issue
  • Schema parsing issue
  • Mapping or normalization issue
  • Rule classification issue
  • Expected business variance