web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / External events stop w...
Small and medium business | Business Central, N...
Suggested Answer

External events stop working, after webhook pinged returned 400 too often

(5) ShareShare
ReportReport
Posted on by MS-04071101-0 10
Hey together, 
so we have created this setup out of BC where we have an external event signaling an external (3rd party) software. We have now encountered the problem, that after the third party software not beeing available for some times, and so returning a 400 Error, the external event has stopped working. 
 
The Page EE Subscription List (3300, List), has an entry stating the EE as not active. 
 
Now we are wondering, on
1. why this would be set-up this way
2. how we can activate the EE again
3. If our conclusion about the Error 400 is correct, what the limits would be and why such thing would be implemented.
 
Customers Production is a BC 25.5.
 
Thanks in advance and I hope, someone can help me.
Best, Max
Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,554 Super User 2026 Season 1 on at
    Good morning, afternoon, or evening depending on your location :)
    Hope you are well today!
     
    Yes, your understanding is correct: Business Central disables external event (EE) subscriptions if the webhook endpoint repeatedly returns HTTP 400-series errors (such as 400 Bad Request). This is a built-in safeguard to prevent system overload and unnecessary retries to unreachable or misconfigured endpoints.
    Why This Happens
    • Business Central monitors the health of webhook endpoints.
    • If an endpoint consistently returns client-side errors (4xx)—especially 400, 404, or 410—the system assumes the endpoint is no longer valid.
    • To maintain performance and avoid unnecessary retries, the EE subscription is marked as inactive in the EE Subscription List (Page 3300).
    How to Reactivate the External Event
    1. Fix the root cause of the 400 errors in your third-party system (e.g., malformed payloads, authentication issues, or endpoint unavailability).
    2. In Business Central:
      • Go to Page 3300 – EE Subscription List.
      • Locate the inactive subscription.
      • Use the “Re-enable” or “Activate” action (if available).
      • If not available, you may need to delete and recreate the subscription.
    What Are the Limits?
    • Microsoft does not publish exact retry thresholds, but based on community feedback:
    • Multiple consecutive 400 responses (e.g., 5–10) can trigger deactivation.
    • The system may retry over a short period before marking the subscription inactive.
    • This behavior is by design to protect system resources and ensure stability.
    Best Practices
    • Always validate your webhook endpoint with test payloads before going live.
    • Implement logging and error handling on the receiving side to catch and resolve issues early.
    • Consider using Azure Functions or Logic Apps as intermediaries to buffer and validate incoming requests.
     
    Note: I collaborated with Copilot to help craft this response for clarity and completeness.
    Hope this helps some!
  • Suggested answer
    Jeffrey Bulanadi Profile Picture
    Jeffrey Bulanadi 9,121 Super User 2026 Season 1 on at

    Hi Max,

    You're asking why your external event subscription in Business Central was marked as inactive after repeated HTTP 400 errors from the third-party webhook endpoint, and how to reactivate it. Based on your setup and the EE Subscription List status, your conclusion is spot on Business Central disables external event subscriptions when the target endpoint consistently returns client-side errors like 400.

    Here’s what’s happening and how to fix it:

     

    1. Why BC disables the subscription

    • When a webhook endpoint returns 400 Bad Request repeatedly, BC interprets this as a persistent failure.
    • To avoid flooding the external system or wasting resources, BC automatically marks the subscription as inactive.
    • This behavior is intentional—it protects both systems and ensures that only healthy endpoints receive events.
     

    2. How to reactivate the external event

    • Go to the EE Subscription List page (Page ID 3300)
    • Select the inactive subscription
    • Choose Actions > Activate Subscription
    • If the endpoint is still returning 400, BC will disable it again—so make sure the external system is ready to receive and process the payload correctly
     

    3. Why 400 errors trigger deactivation

    • A 400 error means the request was malformed or the payload didn’t match what the receiving system expects
    • Common causes include:
      • Incorrect headers or content type
      • Unexpected payload structure
      • Authentication issues (if the endpoint expects a token or key)
    • BC doesn’t retry indefinitely—after a threshold of failed attempts, it disables the subscription to prevent further issues
     

    Here’s a helpful link showing how to configure and troubleshoot external business events and webhook failures:

    External Business Events in Business Central – Fredborg
    Webhook Error 400 – Bobcares
    Troubleshooting Web Service Errors – Microsoft Learn
     

    If you find this helpful, feel free to mark this as the suggested or verified answer.

    Cheers
    Jeffrey

  • Suggested answer
    Jainam M. Kothari Profile Picture
    Jainam M. Kothari 16,538 Super User 2026 Season 1 on at
    Hello,
     
    You can manually reactivate the EE via the EE Subscription List (Page 3300) by selecting the inactive entry and clicking "Activate."
     
    Your conclusion about the 400 error causing the deactivation is correct, though the exact failure threshold isn't publicly documented.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,138 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,279 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,192

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans