📖Investigate system logs

The project's error logs history is stored here. Error logs help you to efficiently identify the problems and errors occurred in your project.

Use system logs to investigate messages associated with app or integration problems.

Find relevant messages

1. Open More → System logs.

2. Set Date from and Date to around the reported problem.

3. Narrow Level, Source, or Action as appropriate.

4. Use Search logs for a relevant term.

5. Review the source/action, message, and date of matching entries.

System logs with Level, Source, Action, date filters, Search logs, and an empty result

The screenshot shows an empty result. Nothing found means no entries matched the current view; it does not prove that the underlying operation succeeded.

Troubleshoot an empty result

Check the app and environment, widen the date range, and remove unnecessary filters. Reproduce the issue with test data and note the exact time. If no relevant entry appears, investigate the identity provider, API, or resource involved as appropriate.

Share useful diagnostics

Include the symptom, reproduction steps, approximate time with timezone, and redacted relevant message. Remove tokens, passwords, cookies, and customer data before sharing.

Use the audit trail for available user activity. Use sign-in troubleshooting when the issue occurs during authentication. Confirm retention and coverage for your deployment rather than assuming logs are permanent.