We have a webhook configured to receive notifications when decision rules are updated in our decision management system. The webhook worked fine in our dev environment but stopped triggering after we promoted to production three weeks ago.
The webhook endpoint is definitely reachable - I can call it manually and it responds correctly. But when business users update decision rules through the Power Platform interface, no webhook events are fired. We’re missing critical rule change notifications that our compliance system depends on.
Webhook URL: https://api.company.com/webhooks/rules
Event Type: DecisionRule.Updated
Status: Active (registered 21 days ago)
I’ve verified the webhook registration shows as active in the Power Platform admin center. Is there an environment-specific configuration that prevents webhooks from firing in production? How can I diagnose why events aren’t being sent?
I tried re-registering the webhook in production but still no events. The registration succeeds without errors, shows as active, but nothing gets sent when rules are updated. Could there be firewall rules blocking outbound webhook calls from the production environment?
This sounds like the webhook registration didn’t carry over properly during environment promotion. Webhook subscriptions are environment-specific and don’t automatically migrate. You need to re-register the webhook in production, even if it shows as active. The registration might be pointing to the wrong endpoint or have incorrect authentication credentials for the prod environment.
Use the API diagnostics endpoint to check webhook delivery logs. You can see if events are being generated but failing to deliver versus not being generated at all. That will tell you if it’s a network issue or a configuration problem with the event subscription itself.
Check if your production environment has webhook event filtering enabled. Some orgs disable webhooks by default in prod for security reasons. You might need to explicitly enable decision management events in the environment settings.
Production environments often have stricter outbound connection policies. Check with your network team if there’s a firewall rule blocking webhook traffic. Also verify your webhook endpoint uses HTTPS with a valid certificate - some environments reject webhooks to HTTP endpoints or self-signed certs.
I’ve debugged this exact scenario multiple times. The issue is almost always one of three environment-specific problems:
1. Webhook Registration Validation
When you register a webhook, Power Platform sends a validation request to your endpoint. In production environments with stricter security, this validation often fails silently. Your webhook shows as “active” but isn’t actually validated.
Test this by checking the API diagnostics endpoint:
GET /api/data/v9.2/webhooks/{id}/diagnostics
Look for validationStatus: "failed" in the response. If validation failed, the webhook won’t fire even though it appears active.
2. Environment-Specific Configuration
Production environments have webhook event filtering that dev environments don’t. Navigate to Power Platform Admin Center > Environments > [Your Prod Environment] > Settings > Integration > Webhook Configuration.
Verify these settings:
“Enable Decision Management Events”: Must be ON
“Event Filter Mode”: Set to “Allow All” or explicitly add “DecisionRule.Updated”
“Webhook Authentication”: Match your endpoint’s expected auth method
Many organizations set prod environments to “Event Filter Mode: Deny All” by default, which blocks all webhook events regardless of individual subscriptions.
3. API Diagnostics Endpoint Usage
The diagnostics endpoint reveals delivery attempts and failures:
GET /api/data/v9.2/webhooks/{id}/deliveries?$top=50
This shows recent delivery attempts, HTTP response codes, and error details. Common issues:
401/403 responses: Authentication mismatch between environments
No delivery attempts logged: Events aren’t being generated (filter issue)
Complete Fix Process
Delete and re-register the webhook in production with explicit validation:
POST /api/data/v9.2/webhooks
{
"url": "https://api.company.com/webhooks/rules",
"events": ["DecisionRule.Updated"],
"validateOnRegister": true
}
Confirm validation succeeds by checking diagnostics immediately after registration
Enable decision management events in environment settings (Admin Center path above)
Test with a manual rule update and check delivery logs within 60 seconds
If deliveries show 401 errors, update webhook authentication headers to match production API credentials
The most common root cause is the environment filter blocking decision management events. Check that setting first before troubleshooting network or authentication issues.