Skip to content

Notification log

Applies to: Owner, Administrator and any role with Notifications.View. Last reviewed: 2026-11-18.

The Notification Log is the record of messages DriveFlow sent, or tried to send, for your school. It is the first place to look when someone says "I never got it".

1. Opening the log

Who: anyone with Notifications.View. The System tile on the Settings page is shown to users with Settings.Manage or Notifications.View, but the page itself needs Notifications.View. It is not available to a SuperAdmin (the log is per school).

  1. In the side menu click Settings.
  2. Click the System tile ("Notification log: every email, SMS and ...").
  3. The page Notification Log opens (/settings/system), newest first.

Screenshot to be added

Screen: Notification Log. Should show: the grid with Status and Channel filters and a Failed row showing its tooltip.

2. Reading the list

Column Meaning
Date When the log entry was created, in your browser's local time
Channel Email, SMS, WhatsApp or Push
Recipient The email address or phone number exactly as stored on the record, or "DriveFlow app (N devices)" for push
Subject The message title; "-" when there is none
Status A coloured chip: Sent (green), Failed (red), Pending (amber). Hover over a Failed chip to read the error.

Filters

Control Use
Status All statuses, Pending, Sent, Failed
Channel All channels, Email, SMS, WhatsApp. Push is not offered as a filter; push rows appear under All channels.
Search recipient or subject... Finds text inside the recipient or the subject. Type an email address, part of a phone number or an invoice number.

The list is paged (at most 100 rows per page from the API).

3. Seeing a message

  1. Click a row.
  2. A dialog opens with the subject as its title and shows To, Channel, Created, Sent (when it was sent) and Status.
  3. If it failed, the error is shown in a red box.
  4. Below that is the message exactly as sent: an email is shown as it looked (in a safe, script-free frame); an SMS, WhatsApp or push message is shown as text.
  5. Click Close.

Attachments are not stored in the log. To see the PDF, open the invoice, receipt or quote.

4. What each status means

Status Meaning
Sent The provider accepted the message: the SMTP server took the email, the SMS or WhatsApp API answered OK, or Firebase accepted the push for at least one phone. It does not prove the person received or read it.
Failed The provider refused or could not be reached, or there were no SMS credits. The error text says why. Nothing was delivered and nothing will be retried.
Pending The entry was created but the outcome was never written. Rare; it means the process stopped between the two steps. Treat as unknown.

Sent does not always mean sent

On a system where the platform has switched the SMS or WhatsApp provider off, messages are still logged as Sent. See SMS notifications section 2.

5. What is and is not in the log

Recorded:

  • Every message sent through the notification engine, one row per channel (email, SMS, WhatsApp, push).
  • Invoice emails (automatic and Send Email).
  • Payment reminder emails (automatic and Send Reminder).
  • Receipt emails (Email Receipt).
  • Quote emails.
  • The "Welcome to DriveFlow" email and the registration alert for your school.
  • Subscription invoice emails from DriveFlow.

Not recorded:

  • New user passwords and administrator password resets.
  • Student portal invites.
  • "Forgot password" emails.
  • The test email from Email Settings.
  • Messages that were never attempted. If a message was switched off, fell in quiet hours, or the recipient had no email address or phone number, there is no row. The reason is only in the server log.
  • A push for someone without the app (no row, by design).
  • The reminders the mobile app schedules on the phone.
  • Document expiry reminders (written without a school, so no school sees them).

An empty search is not a fault

An empty search does not mean the system is broken; it usually means the message was not due, was switched off, or the address is missing. See Notification troubleshooting.

6. Typical error texts

Error text Meaning
"No SMS credits left. Buy an SMS bundle under Settings > Billing." SMS balance too low for this message
"Vodacom SMS send failed with status ...: ..." The SMS provider refused the message
"Meta WhatsApp send failed with status ...: ..." WhatsApp refused it; often the 24-hour rule
"'...' is not a valid destination number." The phone number has no usable digits
"SMTP port 465 (implicit SSL) is not supported. Use port 587 with SSL/TLS enabled instead." The school's SMTP port is 465
An SMTP error such as authentication failed or mailbox unavailable The mail server refused the sign-in or the recipient
"Push notification not delivered: ..." Firebase refused every device
"Push notifications are not configured on this server." Firebase key missing

7. For developers

Table, API and storage details
  • Table: Notifications (entity DriveFlow.Domain.Notifications.Notification): CompanyId, Channel, Recipient, Subject, Message, Status, SentOn, ErrorMessage, plus the base fields (CreatedOn, IsDeleted).
  • There is no link from a log row to the lesson, invoice or student, and no event name. Find rows by recipient and subject.
  • API: GET api/notifications/log (query: pageNumber, pageSize, status, channel, search) and GET api/notifications/log/{id}; both need Notifications.View and return only the caller's company (NotificationLogService).
  • SentOn is only meaningful when the status is Sent; the API returns it as empty otherwise.
  • There is no clean-up job; rows are kept indefinitely. Email rows store the full HTML.
  • Tests: DriveFlow.IntegrationTests/Notifications/NotificationLogTests.cs.

8. Limitations and notes

  • Read-only: no resend button, no export, no delete.
  • No date-range filter and no column sorting.
  • No delivery, bounce, open or read tracking.
  • Students see their own non-failed email, SMS and WhatsApp rows on the portal Messages page; see In-app notifications.