# \[FIXED\] Webhook failures handling **URL:** \ **Category:** Bugs & Issues\ **Created:** [August 4, 2025, 6:36pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349 "2025-08-04T18:36:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [August 4, 2025, 6:36pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349/1 "2025-08-04T18:36:00Z")
Hey there! We’ve been using webhooks over the past few months to send notice of task completions and other fun things to some other systems. It works! Great! However, for various reasons from time to time, the webhook will timeout for an hour or two (system maintenance at the receiving end, etc), and once the webhook fails a certain number of times it just completely deactivates itself. No exponential backoff, no “try again later” logic – just turns itself off. This wouldn’t be so bad if we at least were made aware that webhook failed, but often the only way we know is if things stop syncing, and we use Postman to get all webhooks from Fibery and search for the “failed” status one. We then have to delete it and recreate it. Any way to expose webhook failures in a more visible way, or to add some exponential backoff logic to them? ---
**Author:** ![Sergey\_Truhtanov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sergey_truhtanov/32/13986_2.png) [@Sergey\_Truhtanov](https://community.fibery.io/u/Sergey_Truhtanov)\ **Post date:** [August 6, 2025, 12:41pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349/2 "2025-08-06T12:41:13Z")
Hello. At the moment we retry 5 times with exponential back off with formula `Math.pow(Math.E, retry + 1) * 1000` This is indeed low time, just several minutes on last retry 🤔 . I will increase retry count to 10, which will lead to 3.5 hour total delay before disabling a webhook. Also I’ll make a change, that will send fibery notification to all workspace admins when webhook got disabled due to subsequent failures. ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [August 6, 2025, 3:17pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349/3 "2025-08-06T15:17:31Z")
This is incredible, and this is why I love this software so much. Awesome solution. Thanks for digging into this! 🥳🥳 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 7, 2025, 12:43pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349/4 "2025-08-07T12:43:56Z")
fixed > [@August 7, 2025 / umbrella\_on\_ground Remote MCP Server, tons of small UI improvements](https://community.fibery.io/t/august-7-2025-remote-mcp-server-tons-of-small-ui-improvements/9371): > > Fibery Remote MCP Server MCP Servers are nice, but installation was painfully hard. Now Fibery supports Remote MCP and it means you can install it easily and authenticate via OAuth. Claude (Desktop and Web, paid plans only) and Cursor are supported as MCP Clients. If you want to use Fibery MCP in some other client, let us know. [image] Fibery MCP server includes dozen of tools with the full workspace schema access, advanced querying, entity manipulation, user context, and Fibery user guide sea… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 7, 2025, 5:57pm UTC](https://community.fibery.io/t/fixed-webhook-failures-handling/9349/5 "2025-08-07T17:57:18Z")