Diagnostics & health
Built-in tools for troubleshooting and monitoring workflow health.
Diagnostics report
GET /pfw/v1/diagnostics returns a comprehensive report:
- Plugin version and environment (WP version, PHP version)
- Event registration summary (which hooks are registered)
- Queue statistics (pending, claimed, failed jobs)
- Cron status (last tick timestamp)
- Connected accounts summary
Heartbeat system
A 1×1 pixel injected on every WP admin page pings /pfw/v1/heartbeat to nudge the queue forward between cron ticks. This ensures that even on sites with unreliable WP-Cron, the queue keeps processing.
- Rate limited to once per 30 seconds per IP
- Processes 1 queue job per ping
- Transparent to the admin user
Loopback healthcheck
The plugin can self-initiate queue processing via POST /pfw/v1/loopback/run (HMAC-signed). This is used when the normal cron tick needs a boost — e.g., after a bulk import that creates many pending jobs.
Failure notifications
When a workflow fails and pfw_failure_notification_mode is immediate:
- An email is sent to the site admin (or configured recipients)
- The email includes: workflow name, execution ID, failed node, error message
- A link to the execution timeline in the admin
Support package
For any execution, you can download a support package: GET /pfw/v1/workflows/{id}/executions/{eid}/support
The package contains:
- Full execution timeline (every node, every decision)
- All log entries
- Replay data (can be used to reproduce the issue)
- Environment info at execution time
When reporting a bug, always attach a support package.
Redacted automatically — no credentials or secrets are included.
Redacted automatically — no credentials or secrets are included.