August 20, 2026Cryvis

Handle Cryvis API Errors in Make.com

Configure Make.com Error Handlers for Cryvis HTTP calls—retries, 401/402/422 codes, and soft validation warnings in meta.

Cryvis failures are predictable JSON plus HTTP status codes. Soft validation warnings, however, often arrive as HTTP 200—those need a Router, not an Error Handler.

This post covers Make Error Handlers on the Cryvis HTTP module, retry strategy, and validation warnings. Hub: Make.com + Cryvis. Auth: Bearer authentication.

Error response shape

{
  "success": false,
  "error": {
    "code": "CREDIT_ERROR",
    "message": "Insufficient credits."
  },
  "request_id": "req_..."
}

Map error.code, error.message, and request_id inside the error-handler branch (Slack/Sheets log).

HTTP	Code	Typical cause	Make handler tip
401	AUTHENTICATION_ERROR	Bad/missing Bearer	Break; fix key; no auto-retry storm
403	AUTHORIZATION_ERROR	Permission	Break + alert
402	CREDIT_ERROR	Empty balance	Break; notify billing
400	MISSING_COUNTRY / invalid input	Driver license without `country`, bad multipart	Break; fix scenario
404	UNSUPPORTED_DOCUMENT / UNSUPPORTED_COUNTRY	Wrong type/country	Break; fix Router
422	VALIDATION_ERROR / EXTRACTION_ERROR / CONVERSION_ERROR	Schema hard fail, unreadable file	Break or Resume with flag
502	AI_PROVIDER_ERROR	Upstream blip	Break with delayed retry
500	INTERNAL_ERROR	Server	Break with retry

Attach an Error Handler

On the HTTP module → Add error handler:

HTTP Cryvis
  ├─ happy path → Sheets
  └─ error handler
        → Slack Notify (code, message, request_id)
        → Break (store incomplete execution)

Handler	When
Break	Default for Cryvis—retry after fixing credits/key/file
Ignore	Rare; only if skipping one bad attachment in a batch loop and you accept data loss
Resume	Provide fallback empty collection and continue—use carefully
Rollback	Only if other modules are transactional

Prefer Break for 402/401/502 so incomplete executions remain visible in Make.

Retries

502 / transient network: Break with automatic retry (e.g. 15–60 minutes), limited attempts.
401 / 402 / 400 / 404: Do not tight-loop retry—fix config or credits first.
422 VALIDATION_ERROR (custom hard): Fix schema or document; retrying the same PDF rarely helps.

Soft validation is not an error

Custom extractors (and some flows) return:

{
  "success": true,
  "data": { },
  "meta": {
    "validation": {
      "is_valid": false,
      "warnings": [ ... ],
      "confidence": 0.7
    }
  }
}

HTTP status 200 → Error Handler never runs. Add a Router or Filter:

HTTP (success)
  → Router
       warnings length = 0 → write ERP
       warnings length > 0 → Slack #review → optional write / hold

Schema soft vs hard: Custom extractor schemas. Field design: Extract specific fields.

Multi-file receipt calls can succeed overall while you still want to inspect each results[].meta. Iterate results; treat empty data or validation objects per file. Envelope: Parse API JSON responses.

Logging template (Slack)

Include:

Scenario name + execution ID (Make)
Cryvis error.code / error.message or validation warnings
Cryvis request_id
Source file name (Drive/Gmail)

Support can correlate Console usage with that request_id.

Checklist

Error Handler on every Cryvis HTTP module
Slack/Sheets log includes request_id
402 vs 401 differentiated in the message
Router for meta.validation.warnings
No aggressive retry on auth/credit errors

Multipart mistakes often surface as 400/422—verify field names in Send multipart form data. Full REST setup: Connect REST API.