# X_DB_STATEMENT_TIMEOUT

## Means

the statement ran past its `statement_timeout`

## Typical cause

SQLSTATE `57014` — a sequential scan where an index was assumed, or a plan that changed under a grown table. On the memory driver, a `lock` or `lockKey` waiter past 5 s: usually two locks taken in opposite order

## Fix

add the index this statement needs to the entity (`indexes: [...]`), then `x db gen "add index"`

[Entity and database](/error-codes#entity-and-database)