PagerDuty Error Handlers

The PagerDuty plugin includes built-in error handlers for common PagerDuty API error scenarios.

Built-in Error Handlers

Rate Limit Errors

Triggers: HTTP 429 status

Behavior:

• Maximum retries: 5
• Respects Retry-After header

Example:

// Corsair handles rate limits automatically
await corsair.pagerduty.api.incidents.list({
    limit: 100, 
});

Authentication Errors

Triggers: HTTP 401 status or errors containing invalid credentials

Behavior:

• Maximum retries: 0 (no retries)
• Fails immediately

How to Fix:

1. Verify your API key is valid and not expired
2. Ensure the API key has the required permissions
3. Check if the key was revoked in PagerDuty

Permission Errors

Triggers: HTTP 403 status

Behavior:

• Maximum retries: 0 (no retries)
• Fails immediately

How to Fix:

1. Verify the API key has access to the requested resource
2. Check user role permissions in PagerDuty

Not Found Errors

Triggers: HTTP 404 status

Behavior:

• Maximum retries: 0 (no retries)
• Fails immediately

Network Errors

Triggers: Connection errors, timeouts

Behavior:

• Maximum retries: 3
• Uses exponential backoff

Custom Error Handlers

pagerduty({
    errorHandlers: {
        MAINTENANCE_WINDOW: {
            match: (error) => {
                return error.message.includes("maintenance"); 
            },
            handler: async (error, context) => {
                return {
                    maxRetries: 5,
                    headersRetryAfterMs: 60000, 
                };
            },
        },
    },
})

For comprehensive error handling strategies, patterns, and best practices, see the Error Handling concepts page.