Skip to content

RDoc-3843_taskErrors - document new task errors views and functionality#2450

Open
reebhub wants to merge 7 commits into
ravendb:mainfrom
reebhub:RDoc-3843_taskErrors
Open

RDoc-3843_taskErrors - document new task errors views and functionality#2450
reebhub wants to merge 7 commits into
ravendb:mainfrom
reebhub:RDoc-3843_taskErrors

Conversation

@reebhub
Copy link
Copy Markdown
Contributor

@reebhub reebhub commented May 19, 2026

Issue link

RDoc-3843
RDoc-3844
RDoc-3845
RDoc-3849
RDoc-3775
RDoc-3854
RDoc-3861
RDoc-3851
RDoc-3811

Type of change

  • Content - docs
  • Content - cloud
  • Content - guides
  • Content - start pages/other
  • New docs feature (consider updating /templates or readme)
  • Bug fix
  • Optimization
  • Other

Changes in docs URLs

  • No changes in docs URLs
  • Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

  • No changes in UX/UI
  • Changes in UX/UI (include screenshots and description)

@reebhub reebhub requested a review from Lwiel May 19, 2026 01:54
Comment on lines +113 to +115
* **Persistence** (AI tasks only)
The task could not save its results back to the database. Typical causes include write
conflicts or storage errors.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also occurs when we fail to update process state, so it's not AI tasks only

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

The retention is per task and per table, so a single noisy task cannot push errors out of an
unrelated task. The cap is not configurable.

Errors are also included in the server's debug package as `etl.errors.json`, so support
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI task errors are stored separately

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done


A task recovers automatically as new batches complete. The health state transitions from
`Failed` back to `Impaired`, and from `Impaired` back to `Healthy`, as the running error rate
falls below each threshold. There is no manual "reset" action.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's worth noting we reset health state back to Healthy on task configuration update

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment on lines +222 to +229
`GET /databases/*/tasks/errors` returns errors across all ETL and AI tasks.
`GET /databases/*/etl/errors` and `GET /databases/*/ai/errors` return errors per category.
`DELETE` variants of each path remove errors in bulk, optionally filtered by task name or
category. For example, `DELETE /databases/*/etl/errors?name=<task-name>` clears the errors
of one specific ETL task.
`POST /databases/*/etl/retry-batch` forces an immediate retry of an ETL task currently in
fallback mode.
See [Debug Endpoints](../../server/troubleshooting/debug-routes.mdx#debug-endpoints) for the full reference.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make it a list?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done


<ContentFrame>

### Task health indicators
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe let's mention that only node the task is currently on and nodes that contain any errors are displayed here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

* Retention is per task and per table, so a single noisy task cannot push errors out of
an unrelated task.

* Errors are also included in the server's debug package as `etl.errors.json`, so
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's separate json file with AI tasks errors

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants