Skip to content

Logging (detailed)

This content is for Spring ’26. Switch to the latest version for up-to-date documentation.

Aforza provides a logging service which gives organisations insight into actions undertaken by the application and highlights incorrect configurations early. Logging is enabled by default and is designed not to degrade application performance. Logs are surfaced on the Logs tab where your permissions allow access. Hourly anonymised extracts can be sent for support analysis; you can alternatively persist logs in your organisation-see Company configuration.

Logs contain detailed information about an action undertaken in the application. Logs are typically created for actions that need auditing or configuration diagnosis. Examples include:

  • A warning logged because the user lacked the required permission.
  • A notice logged when company settings were updated.
  • A notice logged when recommendations were fetched from Aforza Cloud services.
  • An error logged when an unexpected fault occurred.

Reviewing logs helps you resolve configuration gaps before they affect large user groups and gives Aforza Support the evidence trail needed for faster diagnosis.

Each log tends to expose:

  • Severity (notice, warning, error)
  • Platform (desktop, mobile)
  • Message
  • Additional detail payloads where captured