Hello,
Thank you for reaching out to Hexnode Connect!
This behavior is completely expected and comes down to how system events, automated provisioning, and timezones are handled within Hexnode:
1. Audit History vs. System Alerts
The Audit History report records operational actions taken directly within the portal (such as modifying devices, policies, users, or technician roles). Events like API key generation are categorized as system alert events. These trigger real-time email notifications via your configured Alert Profiles, but they do not generate a separate, standalone row in the general Audit History table.
2. Event Correlation & Automated Provisioning
Since the Audit History report filtered by your technician account lists the new technician in the Subject column, it confirms that you initiated the action. During technician creation, Hexnode automatically executes a rapid setup sequence in the backend:
- Creating the technician account.
- Assigning the specified role/profile.
- Generating the initial API key tied to that technician setup.
Because these steps occur automatically in quick succession, the account creation logs and the API key alert email are triggered within the same minute.
3. Timestamp Discrepancy
The time difference you noticed is due to timezone formatting: Hexnode email alerts utilize UTC timestamps by default, whereas Audit History reports in the portal display time based on your portal’s configured local timezone.
I hope this clarifies how API key alerts and audit logs operate! Please feel free to reach out if you have any further questions.
Best regards,
George
Hexnode UEM.
What's new 
12 Views
