Audit Logs and Delivery Status
Find out who changed what in your organization, check how emails and texts are being delivered, and replay failed deliveries
Audit Logs and Delivery Status
The Logs page -- "Audit trail and delivery status for your organization" -- answers two questions: what happened, and who did it? and did our emails and texts get through? Find it in the sidebar under Admin › Logs (/dashboard/admin/logs). It requires the organization Admin role.
The page has two tabs:
- Audit Logs -- a history of recorded actions in your organization.
- Delivery Status -- the email and SMS jobs your organization has sent or is sending.
You also land here from the admin dashboard home: Recent activity links to the audit log, and the delivery problems listed under Needs attention open the failed jobs on the Delivery Status tab.
Audit Logs
What Gets Logged
Each entry belongs to a category. These are the categories, in the order the filter lists them, with examples of the actions you'll see:
| Category | Examples |
|---|---|
| User | Roles Updated, Invitation Sent, Org Role Granted, First Login, Delivery Preferences Updated, Claim Link Issued, Claim Link Sent, Claim Link Redeemed, Account Disconnected |
| Group | Group Created, Group Updated, Group Deleted |
| Group Join | Join Request, Join Approved, Join Rejected, Join Rejection Reversed |
| Membership | Member Assigned to Group, Membership Reactivated, Category Updated, Self-Permissions Updated |
| Delegation | Delegation Created, Delegation Revoked |
| Activation | Email Activation, Phone Code Sent, Phone Code Verified |
| Payment | Payment Processed, Manual Payment Recorded, Payment Refunded |
| Registration | Registration Created, Registration Approved, Registration Cancelled, Promoted From Waitlist, Attendee Cancelled, Attendee Refunded, Form Template Saved, Form Template Deleted |
| Organization | Org Updated (branding changes), Org Data Exported, Org Data Imported |
| Calendar | Event Created, Series Created, Event Updated, Series Updated, Event Status Changed, Series Status Changed, Attachment Added, Event Deleted, Series Deleted, Attachment Removed |
| Message | Message Updated, Message Published, Message Scheduled, Schedule Cancelled, Scheduled Send Failed |
| Delivery | Delivery Failed, Recipient Opted Out, Unsubscribed, Delivery Blocked, Delivery Unblocked, Delivery Cancelled, Delivery Replayed |
What Is Not Logged
Some changes never appear in Audit Logs. Don't go looking for them there:
- Website pages -- creating, editing, publishing or deleting them.
- Menus, menu links, and navigation settings.
- Registration forms -- creating, editing, opening or closing, or deleting them. (Saving or deleting a form template is logged, under Registration.)
- Timezone and calendar tag settings.
- Creating, copying or deleting a message. (Editing, publishing and scheduling one are logged, under Message.)
Reading a Row
Each row has four columns:
- Time -- when it happened, in your browser's time.
- Action -- what happened. A red badge means the action failed.
- Target -- the email address the action was about, when there is one, and By: followed by who did it.
- Status -- a green tick for success or a red cross for failure, with the error message if there was one.
Rows with an arrow at the right-hand end can be clicked to show more detail -- for example the exact changes that were made, or the stored identifier of the person who did it.
By: usually shows a person's name. Some entries show one of these labels instead:
| Label | Meaning |
|---|---|
| System | Hubara did it automatically -- for example, a delivery that failed or a scheduled message that was sent. For a scheduled message, the row's details also include the stored identifier of the person who scheduled it. |
| Registration form | It came through a registration form. |
| Unsubscribe link | Someone used the unsubscribe link in an email. |
| Unknown | Hubara could not tell who did it. |
| Admin (not recorded) | An admin did it, but Hubara did not record which one. This appears only on older entries for publishing, scheduling or cancelling a message, or changing branding. Newer entries for those actions name the person. |
Filtering
The category dropdown above the table is the only filter. It starts on All Categories; pick a category to see only its entries. Entries are listed newest first, and the line above the table reads "Showing N audit log entries". Click Load More at the bottom to see older entries.
Answering "Who Changed This?"
- On the Audit Logs tab, pick the category the change belongs to -- for example Group for a renamed group, or User for a changed role.
- Scan the Action and Target columns for the change.
- Read the By: line in that row.
- Click the row (if it has an arrow) to see exactly what changed.
The log has limits:
- It only covers the areas listed under What Gets Logged.
- Older entries for publishing, scheduling and cancelling a message, and for branding changes, read Admin (not recorded), so for those the log cannot tell you which admin it was. Newer entries name the person.
- Entries are set to expire 90 days after they are written, so don't rely on finding anything older.
Delivery Status
Every email and text message Hubara sends for your organization is a delivery job. The Delivery Status tab shows those jobs.
Active and Archive
The tab has two views, switched with the Active and Archive buttons:
- Active -- jobs that are waiting to send or sending now. Completed, failed, opted-out and cancelled deliveries are moved to the Archive view.
- Archive -- delivery history: jobs that completed, failed, were not sent because the recipient opted out, or were cancelled.
Four summary cards sit at the top: Email Jobs (recent), Failed Emails, SMS Jobs (recent) and Failed SMS.
When there are failed jobs, a Failed Deliveries card lists them: "Deliveries that permanently failed. Some exhausted their retries; others failed on the first attempt because the address or number cannot receive them." Each row shows the type (Email or SMS), the destination, how many attempts were made, and the error.
Below that, Recent Deliveries (in Active) or Archived Deliveries (in Archive) lists jobs with a status badge:
| Status | Meaning |
|---|---|
| Pending | Waiting to send. |
| On hold | Delivery for your organization is paused because of a credentials problem; it sends once the problem is fixed. |
| Processing | Sending now. |
| Completed | Sent. |
| Failed | Could not be delivered. |
| Opted out | Not sent, because the recipient asked not to receive these. Nothing to fix. |
| cancelled | Hubara support cancelled the delivery before it was sent. |
For the delivery status of one particular message, open the message itself -- see Sending Messages.
When Delivery Is Blocked
If Hubara can't use your organization's email or SMS account -- for example its credentials are missing or are rejected by the provider -- it stops sending on that channel for your whole organization. A red banner appears at the top of the Delivery Status tab, for example:
Email delivery is currently blocked for your organization. Reason: … All pending email jobs are paused until this is resolved. Please contact Hubara support. They will update your organization's email credentials and re-enable delivery.
While delivery is blocked, every pending email (or text, for the SMS banner) shows On hold -- nothing on that channel goes out until delivery is turned back on. Held deliveries send automatically once it is.
The one thing to do is contact Hubara support. Only support can update your organization's email or SMS credentials and turn delivery back on; there is no setting for this in your dashboard.
Blocking and unblocking are recorded in Audit Logs under Delivery as Delivery Blocked and Delivery Unblocked.
Replaying a Failed Delivery
Warning: Replaying re-sends the email or text to a real person, at the same address or number it failed on -- the one shown in the confirmation window. Only replay once the cause is fixed and that address is still right -- for example support confirming delivery is working again. If the address itself was wrong, the person needs to correct it in their own profile, and that does not change this delivery; send them the message again once it's fixed.
- On the Delivery Status tab, switch to Archive. Failed jobs only appear there, and the Replay button only appears there and only for Admins.
- In the Failed Deliveries card, click Replay on the row you want to re-send.
- The Replay failed delivery? window asks you to confirm: "Re-send this email to … ? The job will be restored to the active queue and retried."
- Click Replay. The job leaves the Archive view and goes back into the Active view to be sent again.
Each replay is recorded in Audit Logs under Delivery as Delivery Replayed.
If delivery is still blocked when you replay, the page shows:
Circuit breaker is open for this org; the job will not process until the breaker is reset.
That means delivery on that channel is blocked for your organization. The job is back in the queue but will show On hold until Hubara support turns delivery back on -- contact them.
Troubleshooting
| Problem | What to check |
|---|---|
| A change I expected isn't in Audit Logs | That area may not be recorded -- see What Is Not Logged -- or the entry is older than 90 days and has expired. Also check the category dropdown is not filtering it out. |
| By: says Admin (not recorded) | The entry is an older one for publishing, scheduling or cancelling a message, or for a branding change. Back then Hubara recorded that an admin did it, but not which one. Newer entries name the person. |
| I can't click a row to see more | Rows without an arrow have no extra details to show. |
| There is no Replay button | You are in the Active view -- switch to Archive -- or there are no failed deliveries (the Failed Deliveries card only appears when there are some). |
| Messages are stuck on Pending | Look for a red "delivery is currently blocked" banner at the top of the Delivery Status tab. If it's there, contact Hubara support. |
| Replay failed again with the same error | The replay went to the same address or number that failed before. Ask the person to correct it in their own profile (see Your Profile and Contact Details), then send them a new message. |
| "Circuit breaker is open for this org…" after replaying | Delivery is blocked for your organization. Contact Hubara support; the replayed job sends once they turn delivery back on. |