Skip to content
Laritor docs

Notifications

The Notifications resource provides a paginated overview of every notification dispatched by your application. Use this page to confirm successful deliveries, diagnose failures, and navigate directly to the context (request, job, command, etc.) where each notification originated.

Navigation: Access Notifications via the sidebar under the “Notifications” section.

1. Notifications Index Table

Section titled “1. Notifications Index Table”

By default, the Notifications page displays 25 entries, ordered by Sent At in descending order (most recent first). Scroll down and click Load More to retrieve additional records.

1.1 Columns

Section titled “1.1 Columns”

  1. Sent At

    • Timestamp when the notification was dispatched (e.g., 2025-05-30 17:05:32).

  2. Notification

    • The class or identifier of the notification (e.g., OrderShippedNotification, PasswordResetNotification).

  3. Notifiable

    • The entity that received the notification, typically referencing a user or model ID (e.g., User #42). The notifiable may include a user’s name or email in the display.

  4. Occurrence

    • The context in which this notification was triggered:
      • Request (e.g., Request #1023)
      • Command (e.g., Command backup:run)
      • Scheduled Task (e.g., Task daily:report)
      • Queued Job (e.g., Job ProcessInvoiceJob)
    • Clicking the occurrence link navigates to the corresponding details page (e.g., Request Details), where you can view the full event timeline related to this notification.

2. Filters

Section titled “2. Filters”

Above the Notifications table, a set of filter controls helps you narrow down the results:

  1. Search (Notification / Notifiable)

    • A free-text search field that matches against both the Notification class name and the Notifiable display (e.g., searching “OrderShipped” will match all OrderShippedNotification entries).

  2. Date Range

    • Select Start Date & Time and End Date & Time to show only notifications sent within that interval.

Tip: Combine Search and Date Range to find all password reset notifications sent during a specific support window.

3. Load More

Section titled “3. Load More”
  • The Notifications table initially shows the 25 most recent notifications.
  • Click Load More at the bottom to fetch the next batch of 25 entries, ordered by Sent At descending.
  • This incremental loading ensures a fast initial page load while still providing access to your entire notification history.

4. Best Practices

Section titled “4. Best Practices”

  • Confirm Key Notifications

    • Use the Search filter to locate critical notifications (e.g., AccountActivatedNotification, InvoicePaidNotification) and verify they were sent as expected.

  • Audit Recipient Coverage

    • Filter by Notifiable to ensure that specific users or entities have received the notifications they should (e.g., support team email addresses).

  • Diagnose Missing Notifications

    • If an expected notification isn’t listed, check the associated occurrence (request, job, or task) for errors or exceptions—often visible in Logs or Exceptions.

  • Track Scheduled Notifications

    • When notifications are dispatched from scheduled tasks, narrow your Date Range to the task’s run window (for example, the minutes following a daily cron) to confirm successful execution.

  • Correlate with Parent Context

    • Click the Occurrence link to jump directly into the detailed timeline of the sending event (request, command, etc.) and review related database queries, log entries, or external calls.

  • Monitor Volume Trends

    • Over time, use Load More to load historical notifications and observe patterns—such as spikes in password reset notifications after a feature release.

By leveraging the Notifications index, its filters, and occurrence links, Laritor helps you ensure that every user- or system-generated notification is delivered correctly and that any sending issues can be traced back to their origin.