---
url: "https://vueda.dev/v3/reference/api/py/vueda.history.checks.md"
title: "history.checks"
---

# history.checks

## Overview

System checks for the history backend's configuration.

## `check_history_middleware` {#check_history_middleware}

Report a middleware stack that cannot name the action behind a request.

``get_defaults`` places the middleware correctly, but a project owns its own ``MIDDLEWARE`` and
can replace or reorder that list. Both faults here are warnings rather than errors, because a
request still records its events either way. What goes missing is the identity associating the
events of one request with each other, or the user who caused them.

Any ``HistoryMiddleware`` subclass satisfies this, because a project may extend VUEDA's to
record metadata of its own.

### Signature {#check_history_middleware-signature}

`check_history_middleware(app_configs, kwargs)`

#### Parameters {#check_history_middleware-parameters}

| Name | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| <span id="check_history_middleware-param-app_configs">app_configs</span> |  | yes |  |  |
| <span id="check_history_middleware-param-kwargs">kwargs</span> |  | no |  |  |

### Source {#check_history_middleware-source}

`server/vueda/history/checks.py:25`

## Source

`server/vueda/history/checks.py`