System Logs
System Logs
When something goes wrong — an integration fails, a background job errors out, an API call Returns unexpected results — System Logs is your first stop. It gives you a real-time, read-only feed of application events recorded by CifraHQ, so you can diagnose problems quickly without needing server access or a support ticket.
Where to find it
Go to Setup > System > Logs.
System Logs, application errors and audit events for this tenant.
Reading a log entry
| Column | What it shows |
|---|---|
| Date | How long ago the event occurred (e.g., "5 minutes ago") |
| Source | The service or component that generated the entry — useful for pinpointing whether an error came from an integration, a background job, or the API |
| Type | Severity or category (e.g., Error, Warning, Info) — filter by Error to focus on actionable problems |
| Message | A summary of the event — click to expand the full message, stack trace, or context |
Click any entry's Message cell to expand the full detail. Click Hide to collapse it.
Clearing logs
Click Clear in the toolbar to delete all current log entries. Do this after you've resolved an issue and want a clean slate — making it easier to spot new problems if they recur.
Tips
- Logs are sorted newest-first, so the most recent events are always at the top.
- Use the grid's search and filter to narrow down by Source or Type when you're chasing a specific integration failure or background job problem — this saves you from scrolling through unrelated info-level entries.
- When contacting CifraHQ support about an error, copy the Source, Type, Date, and full expanded Message text. This gives support everything needed to reproduce and fix the issue faster.
Related: Audit Trail · Tenant Configuration · User Sessions · Webhooks · Database Backups · Workflows
Was this page helpful?