> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/integration/web-push/wordpress-plugin/activity-log.md).

# 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

1. Navigate to the **Pushly** settings page in your WordPress admin sidebar
2. Open the **Debugging** section at the bottom of the Settings tab
3. Toggle **Debug Logging** to on
4. Click **Save**

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2F5MAVyqphmQrOGPE9JMP9%2FScreenshot%202026-04-16%20at%202.38.42%E2%80%AFPM.png?alt=media&amp;token=6f530ca1-bc3f-4d35-9092-104365da47e7" alt=""><figcaption></figcaption></figure>

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.

{% hint style="info" %}
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.
{% endhint %}

### 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.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FiQPQETGBYwqgnmVQ5gzl%2FScreenshot%202026-04-16%20at%202.41.22%E2%80%AFPM.png?alt=media&amp;token=769e9d6e-d2a7-4e7e-814e-dd7f1d57fe4a" alt=""><figcaption></figcaption></figure>

### Exporting the Log for Support

If you need to contact Pushly support about a notification issue:

1. Go to the **Activity Log** tab
2. Click **Download Log** to save all log entries as a text file
3. 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:

| Event Type           | What It Means                                                      |
| -------------------- | ------------------------------------------------------------------ |
| `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.

{% hint style="warning" %}
Clearing the log is permanent and cannot be undone.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/integration/web-push/wordpress-plugin/activity-log.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.