Skip to main content
Kadoa distinguishes between critical errors that need your attention and normal situations like empty results. Using self-healing technology, Kadoa automatically recovers from most errors without manual intervention.

Understanding Runs vs Workflows

  • Run: A single execution of your workflow at a scheduled time
  • Workflow: The configuration that schedules and manages runs
When errors occur, they affect individual runs - your workflow schedule continues regardless.

Error Categories

Critical Errors (Run Fails)

These errors cause the run to fail with status FAILED. You’ll receive workflow_failed notifications.
Error CodeDescriptionCommon Causes
BLOCKED_ACCESSAccess denied to the websiteGeo-blocking, authentication required, IP ban
MAINTENANCESite under maintenanceScheduled maintenance, temporary outage
TECHNICAL_ERRORWebsite server errorHTTP 500, 502, 503 errors
DATA_VALIDATION_ISSUES_THRESHOLD_REACHEDToo many validation issues detectedData quality below configured threshold
KADOA_INTERNAL_ERRORInternal processing errorInfrastructure issue (rare)
OUT_OF_FUNDSInsufficient creditsAccount needs credit top-up
NOT_SUPPORTEDCannot process this sourceSite structure incompatible

Non-Critical Errors (Run Completes)

These are informational errors. The run completes successfully as these represent valid extraction scenarios.
Error CodeDescriptionWhat It Means
CONFIRMED_NO_DATANo data found on pageThe page legitimately contains no data matching your schema. Empty results are valid.
PAGINATION_INCOMPLETEPartial data extractedSome pagination pages might have been missed, but data was successfully extracted from accessible pages.

Error Response Format

{
  "errors": [{
    "errorCode": "BLOCKED_ACCESS",
    "message": "Access blocked by website security",
    "timestamp": "2025-01-15T10:30:00Z",
    "context": {
      "url": "https://example.com/page",
      "httpStatus": 403
    }
  }]
}

What Happens When Errors Occur

For Critical Errors:

  1. Run marked as FAILED - You’ll see the failed status in your dashboard
  2. Kadoa retries automatically - Self-healing technology attempts recovery on next scheduled run
  3. Ops team is notified - Critical errors are flagged for investigation
  4. Contact support if urgent - Provide workflow ID for expedited help

For Non-Critical Errors:

  • Run completes normally - No intervention needed
  • Data is preserved - Previous data remains unchanged
  • Monitor results - Review extracted data for completeness
I