Run and cancel a query
Press ⌘ / Ctrl + Enter or click Run query to run the active tab. While it runs, the button turns into Cancel. Every query has a 20-second timeout, shown under the editor as “Queries time out after 20 seconds”.
Results appear below the editor with the row count and the time the query took in milliseconds.
Run a query
- Type in the editor. It uses SQL highlighting for MySQL and ClickHouse, JSON for MongoDB and plain text for Redis, Kafka and Kubernetes.
- Press ⌘ / Ctrl + Enter, or click Run query. The shortcut works inside the editor and anywhere else in the workbench.
- To run the same query again, click the refresh button in the Results header (Refresh query).
Each tab runs independently. You can start a query in one tab and keep editing in another.
What each engine accepts
| Engine | Query format |
|---|---|
| MySQL | SQL, run in a read-only transaction |
| ClickHouse | SQL, sent with readonly=1 |
| MongoDB | A JSON find document |
| Redis | An allowlisted read command, or a JSON array of arguments |
| Kafka | A topic name, or topics for all |
| Kubernetes / K3s | get <resource> [namespace] |
See What is read-only in DevOpsPad for how each engine enforces this.
Cancel a running query
Click Cancel. The tab shows “Query cancelled.” and any result that arrives later is discarded. Closing the tab also cancels its query.
Cancelling stops or abandons the client request. Depending on the engine, the server may continue until its own timeout. For example, a heavy MySQL query may keep running server-side after DevOpsPad has given up on it. Add server-side limits (such as max_execution_time in MySQL) when that matters.
When a query fails
The results area shows “That query didn’t go through.” with the server’s error message. Fix the query or the connection and run it again. Failed runs also appear in Query history with the error.
The connection header shows the outcome of the latest request: “Last response at …” after success, “Last request failed” after an error. This is the status of the last real request, not a live health check.
Limits
- 20-second outer timeout per query. Some drivers also have shorter connection timeouts.
- Results are capped at 500 rows or documents and 8 MiB. See Why results stop at 500 rows.
- Write statements are rejected or fail by design. See What is read-only in DevOpsPad.
Frequently asked questions
Does cancelling a query stop it on the server?
Not always. Cancelling stops or abandons DevOpsPad's request, but a database server may keep working until its own timeout. Use server-side limits for long analytical queries.
Why did my query stop after 20 seconds?
Every query has a 20-second outer timeout in DevOpsPad. Narrow the query, add a LIMIT or an index, or run long reports with a dedicated tool.