Activity Log
The Pushly plugin includes a built-in Activity Log that records every step of the notification send process. When a notification doesn't send as expected, the Activity Log shows exactly what happened and why — making it easy to diagnose issues without contacting support.
Enabling Debug Logging
Navigate to the Pushly settings page in your WordPress admin sidebar
Open the Debugging section at the bottom of the Settings tab
Toggle Debug Logging to on
Click Save

Once enabled, the plugin will record detailed log entries every time a post is published or updated. An environment snapshot is automatically captured when logging is first enabled, providing useful context about your WordPress and plugin configuration.
Log entries are written in a single batch at the end of each request and are automatically cleaned up after 14 days or when the log reaches 5,000 entries.
Viewing the Activity Log
Click the Activity Log tab on the Pushly settings page to view recorded log entries. Each entry includes:
Timestamp — when the event occurred, displayed in your local timezone
Severity — the importance level of the event (debug, info, warning, or error)
Event Type — a machine-readable identifier for the event (e.g.,
send_flow_start,api_response)Message — a human-readable description of what happened
Log entries are displayed in reverse chronological order (newest first), with 50 entries per page.

Exporting the Log for Support
If you need to contact Pushly support about a notification issue:
Go to the Activity Log tab
Click Download Log to save all log entries as a text file
Attach the downloaded file to your support ticket
The exported file includes all recorded log entries with timestamps, severity levels, and full message details. This gives the support team everything they need to diagnose the issue without requiring access to your WordPress admin.
You can also click Copy to Clipboard to copy the entries currently visible on the page.
Understanding Log Entries
When a post is published, the plugin logs each decision point in the notification send flow. Here are the most common entries you'll see:
send_flow_start
The notification send process has started for a post
meta_check
Whether the "Send Notification" checkbox was checked
duplicate_check
A notification was already sent for this post
notification_build
The notification payload was assembled
api_request
The notification was sent to the Pushly API
api_response
The API responded — check the message for success or error details
If a notification fails to send, look for entries with error severity. The message will include specific details like HTTP status codes and error messages from the API.
Clearing the Log
Click Clear Log to remove all log entries and start fresh. This is useful when you want to isolate a specific issue — clear the log, reproduce the problem, then review or export the new entries.
Clearing the log is permanent and cannot be undone.
Last updated