Developer Logs

Basics #

Developer Logs help you debug integrations and client‑side usage. You can see requests coming from your site and apps, filter by type, and drill into the details to spot issues quickly.

Find it in my.clerk.io under Developers > Logs for the Store you are working on.

Using filters and search #

• Start with the type filter to focus on errors and warnings while deploying.
• Use the search bar to find specific messages, endpoints, or identifiers.
• Combine search and type filtering; counts update to reflect the active filters.

Sorting #

Click the table headers or use the sort menu to order by:

• Time (default, newest first)
• Source (e.g. Clerk.js, API, backend jobs)
• Type (Error/Warn/…)
• Message (alphabetical)

Sorting happens on the backend so the order is always consistent with the full dataset—even when paginating.

Pagination and performance #

Results are loaded page by page from the server. When new data arrives while you are browsing, older pages won’t be re‑requested unless needed. Duplicate requests are ignored to keep the UI responsive.

Empty states #

If no entries match your filters, you’ll see a clear empty state with suggestions to adjust filters or time range.

Tips #

• Use Error and Warn during rollouts; switch to Info/Debug for deeper investigations.
• Click Details to copy IDs, payloads, or timestamps when opening a support ticket.