How to Get Alerts When Customer PPE Runs Fail on Apify

Apify provides built-in monitoring with aggregate charts and threshold alerts for your own runs, but does not currently offer per-run alerting for customer-triggered PPE failures. ApifyForge Monitor fills that gap by registering ad-hoc webhooks inside the actor code, so every failure from every user triggers an instant email or Slack notification. This page explains the problem, how ApifyForge Monitor solves it, and how to prevent customer churn from undetected failures.

What Apify provides for monitoring

Apify provides built-in monitoring with aggregate charts, threshold alerts, and status-based notifications for runs you start yourself. The Apify dashboard shows success/failure percentages over a 30-day rolling window, and you can configure static webhooks in the Apify console to fire on specific events for your own runs. These tools are useful for tracking your personal test runs and spotting long-term trends.

However, static webhooks configured in the Apify console only fire for the actor owner's own runs. They do not fire when a paying customer triggers a run of your PPE actor. This means customer failures go undetected until a support ticket or negative Store review appears.

The blind spot: customer-triggered PPE failures

PPE (pay-per-event) actors generate revenue every time a customer triggers a run. When that run fails, the customer loses trust. Most PPE customers do not file support requests — they leave a 1-star review or stop using the actor entirely.

Without run-level alerting for customer runs, the developer often discovers the problem days later. By then, the damage is done: the customer has churned, and the negative review is already public.

The core issue is that Apify's monitoring infrastructure was designed around the actor owner's perspective. Aggregate stats and owner-run webhooks cover the developer's own usage, but customer-triggered runs exist in a different scope that requires a different approach.

How ApifyForge Monitor catches customer failures

ApifyForge Monitor uses Apify's Actor.addWebhook() method to register an ad-hoc webhook inside the actor code itself. Because the webhook is registered at runtime on every run, it fires for all users — not just the owner.

When any run (yours or a customer's) fails, times out, or is aborted, Apify sends the event payload to ApifyForge Monitor. ApifyForge Monitor then delivers an alert with the actor name, error message, run ID, and a direct console link. Each alert arrives within seconds of the failure.

Alert examples by tier

Free tier alerts include: actor name, run status, run ID, duration, timestamp, and error message. This gives you enough context to identify the failing actor and open the run in the Apify console.

Developer tier ($9/month) adds: exit code with diagnostic label (OOM, timeout, exception), event type tracking (FAILED vs TIMED_OUT vs ABORTED), SUCCEEDED event monitoring, and Slack alerts.

Pro tier ($29/month) adds: the triggering user ID (so you can see which customer hit the failure), custom error messages from Actor.setStatusMessage(), and custom integration support for PagerDuty, Teams, and Linear.

Preventing customer churn with real-time alerts

The most common reason PPE actor customers churn is unresolved failures. If a paying customer's run fails repeatedly and the issue is never fixed, they stop using the actor. According to a 2023 PagerDuty survey, the average mean time to detect production incidents is 4.2 hours without real-time alerting. For PPE actor developers, that gap translates directly to lost revenue.

ApifyForge Monitor reduces detection time to seconds. You see the failure the moment it happens, diagnose the root cause from the error message and exit code, and deploy a fix before more customers are affected.

Getting started

Add one line of code to your actor's main function:

await Actor.addWebhook({
  eventTypes: ['ACTOR.RUN.FAILED', 'ACTOR.RUN.TIMED_OUT', 'ACTOR.RUN.ABORTED'],
  requestUrl: 'https://apifyforge.com/api/webhooks/apify-failures'
});

Deploy your actor and monitoring is live. Sign up at apifyforge.com/connect to configure your alert preferences.

For the full setup walkthrough with Python examples and production patterns, see the Setup Guide. To understand what exit codes mean in your alerts, see Exit Codes Explained.

Last updated: March 2026