Operations
Logs
Every request to your Project, and every function run, is written to its logs. Filter them to find a problem in seconds.
Find what you need
The Activity chart above the list shows how many requests arrived over the chosen range. Select Refresh to fetch the newest entries.
| Filter | Choices |
|---|---|
Level | All, Debug, Info, Warning, Error |
Time range | 24h, 7d, 30d |
Search | Any text, such as a path, a status code, or a user id |
Client apps only | Shows only calls from your apps and hides console traffic |
Read an entry
Open any row to see the method, path, status, duration, and full details. Use Copy JSON to share it, or export the list as a CSV file.
Write your own log lines
Anything a function prints with console.log appears in that function's logs, next to its duration and result.
console.log("order received", { orderId: $data.id });Common status codes
| Code | Usually means |
|---|---|
400 | The request body or filter is invalid |
401 | No valid sign-in was sent |
403 | Signed in, but an access rule said no |
404 | The record, table, or address doesn't exist |
429 | Too many requests in a short time |
5xx | Something failed inside the Project. Check function logs and recent changes |
Keep logs safe
Never log passwords, tokens, API keys, or personal data. Anyone with access to the Project can read its logs. How long logs are kept depends on your plan.
Fix it yourself. The link below opens this file in GitHub's editor and forks the repository for you if you need one, and your change becomes a pull request without leaving the browser.