handle business central webhook notification retries, collection batching, and unsupported-entity checks
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Query GET .../webhookSupportedResources?$filter=resource eq 'v2.0*' to confirm an entity supports webhooks before subscribing
Design the notificationUrl endpoint to accept a payload whose value array can contain notifications from multiple subscriptions at once
Distinguish changeType values created, updated, deleted from collection, which signals bulk changes and includes a $filter to re-query affected records
Return one of 408, 429, or a 5xx status if you cannot process a notification so Business Central retries
Expect any other error status to cause the subscription to be deleted outright, with no retry
Known gotchas
Business Central delays a notification by 30 seconds after the first change and can coalesce up to 1,000 changes into a single collection notification before falling back to per-record notifications
Retries continue for only 36 hours after a delivery failure, after which the notification is dropped
Power Automate's Business Central connector cannot process collection notifications at all, so flows silently won't fire once the 1,000-record threshold is crossed
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?