Starting with version 11.6, which is currently being rolled out to production, we will automatically disable webhooks where scripts repeatedly fail.
This behavior has always applied to standard webhooks (HTTP), and now we are introducing the same mechanism for CRMScript-based webhooks.
To help you monitor and respond to errors, we strongly recommend enabling error email notifications.
For CRMScript webhooks, you can configure this using:webhook.SetErrorsEmail("username@domain.com");
and to check current webhooks errorsEmail:
webhooks[i].GetErrorsEmail();
You can find more on configuring error notifications on docs.superoffice.com
Please review your webhook configurations and take advantage of this functionality to avoid disruptions.
Alles Antwoorden (3)
I was testing a webhook script today (in 11.6), and suddenly it did not execute, after a few additional tests I realized it did not run at all, and the state was now 3 (TooManyErrors).
I only testet af few times. What is the limit of fails before "TooManyErrors" ?
It felt a little "too sensitive" in test, that it was disabled before I located the error in the script (using log to log where it failed).
For scripts in production it sounds like a good idea to disable (with email notification).
I logged into a customer's environment and observed both webhooks were marked as error state (3).
While investigating, the code showed no obscure logics to me. Further investigating, I somehow got stuck as the "Webhook_usage" table does not really provide me with relevant info:
How to troubleshoot/debug after the webhook was already marked in state 3? Can I figure out what was causing the state-change or should I always evaluate based on the code written in CRMscript?
Normally the last error is of use, but due to a different bug, the only error message you have in some instances is the one you are seeing now, see bug:
https://community.superoffice.com/en/product-releases/bugs-wishes/product-issue/?bid=89381&azure=1