July 2026

Updates released in July 2026.

App Logs

July 23, 2026 — Persistent app event logs — a structured, queryable log for every app

Your apps now have a real logging channel of their own. Alongside browser console output and low-level ERP API calls, apps can emit structured events that are stored on the server, searchable, and available to both you and the App Builder for later analysis.

• Three log streams, one place to view them — open an app's ⋯ menu → Logs to see:
  • ERP API — every Domain API call the app makes through the proxy. Optional and time-boxed: enable it on the app for a defined window when you need to trace a specific issue, and it turns itself off automatically.
  • App events — the new persistent, structured log written by the app itself (see below). Stored for 3 days, searchable, and shared with the App Builder.
  • Console — a live mirror of the app's browser console output. Session-only, never sent to the server; great for real-time debugging while you're using the app.
• Ask the App Builder to log the important things — say things like "log a warning when the discount is over 20%", "log an error if the invoice fails to save, with the customer id", or "log info every time a report is exported". The Builder wires the log calls into the right places for you.
• Structured, not just text — each entry has a level (info / warn / error), a short message, and an optional JSON payload with whatever context matters (ids, amounts, user choices…). You can filter and search by any of it.
• Click any entry for the full detail — long URLs, request/response bodies, arguments and errors open in a copyable, monospace dialog — no more truncated text.
• The App Builder reads the same logs — when you tell the Builder "the export sometimes fails, please investigate", it queries the app's own event log and uses the entries to diagnose the behaviour. You don't have to open the Logs tab yourself unless you want to.
• Safe by default — App events are visible to the app's owner and admins only. Quotas keep noisy apps from filling the log (roughly 1,000 events per day and 60 per minute per app), and entries auto-expire after 3 days.

When to use which log

• Use App events for anything you want to keep, search, or have the AI analyze later — business actions, unusual conditions, failures with context.
• Use ERP API logging when you're specifically troubleshooting how the app talks to ERP.net. Turn it on for a limited window, then let it switch off.
• Use Console for live, in-the-moment debugging while you have the app open. Nothing is persisted.

You don't need to view the logs yourself to benefit from them — just ask the App Builder to look. The tab is there for when you want to see what's happening with your own eyes.