> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/faq/database-is-locked.md).

# Database is locked

When using Singularity with its default database backend (SQLite3), you might encounter the "Database is locked" error message.

## Why Does This Happen?

SQLite3 operates by using a file as its database. Every time a write operation is made, SQLite3 locks this file. If multiple write operations are attempted concurrently, the "Database is locked" error surfaces.

## What Should You Do?

* **Automatic Retry**: Singularity is designed to automatically retry operations that produce this error. Therefore, in many instances, you can safely ignore this error message.
* **Software Hang**: If you believe Singularity has become unresponsive due to this error, please report it as a bug.

## Production Recommendations

SQLite is suitable for development or light workloads, but it's not recommended for Production environments. For guidance on deploying Singularity in a Production environment with a more robust database backend, refer to the [Deploy to Production guide](/singularity/installation/deploy-to-production.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://data-programs.gitbook.io/singularity/faq/database-is-locked.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.