Handle a failed Dosya node in n8n

Interpret Dosya node status text, bounded retries, Continue On Fail output and plan or permission refusals before replaying a workflow item.

Last reviewed

Read both the node’s error message and description before replaying an item. The transport keeps Dosya’s human-readable refusal where possible, adds a recovery hint, and limits automatic retries to requests that are safe to repeat.

Four-step workflow for recording the node error, resolving a 403 refusal, following Retry-After, and deciding whether replay is safe.
Four-step workflow for recording the node error, resolving a 403 refusal, following Retry-After, and deciding whether replay is safe. Open full-size screenshot.

Steps

  1. Open the failed execution and record the node name, item index, HTTP code, message, description and run time. Redact the API key and public URLs before sharing diagnostics.
  2. For dosya.dev did not accept the API key (401), replace a mistyped, expired or revoked key. Re-running with the same credential cannot restore it.
  3. For 403, act on the exact refusal: Full access is required for writes; a folder anchor cannot use REST; membership permissions and workspace pinning still apply.
  4. For 404, verify the mapped ID and whether the target was moved to Trash or hidden from the key. For 413, compare the file with plan, workspace and key per-file limits.
  5. For 429, follow the displayed Retry-After. The node tries at most three attempts and sleeps only when the wait is 30 seconds or less; longer waits are reported for a Wait node or later run.
  6. Decide whether to replay. Idempotent reads/folder creation and upload requests with an idempotency key can retry transient transport errors and 502/503/504; share creation cannot.

With Continue On Fail, each failed input becomes an item shaped like { "error": "…" } with its paired input index, and later input items continue. Without it, the node throws and stops. A successful earlier item is not rolled back when a later item fails.

Reference for “Handle a failed Dosya node in n8n”: Dosya n8n integration overview page.
Reference for “Handle a failed Dosya node in n8n”: Dosya n8n integration overview page. Open full-size screenshot.

Expected result

The corrected run either completes or emits an intentional error item for each failed input. Retries remain bounded, long server waits are respected, and potentially completed non-idempotent actions are inspected before another request.

Could not reach dosya.dev on a non-idempotent step explicitly warns that work may already exist. Storage messages beginning You’ve used … require freeing plan storage or upgrading; a workspace storage-limit sentence requires its administrator to raise that separate cap.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.