Webhook error

Hello, hoping someone has suggestions to get around a Sugar error/bug (https://portal.sugarondemand.com/#supp_Bugs/82879)  that hasn't been addressed.

We've created several webhooks to fire when we add/update several types of records (Contacts, Accounts, etc.). We've found that if the record in the specific module is being updated, the webhook fires correctly and passes the appropriate JSON info to the destination. However, if the record is being ADDed for the first time, the webhook is called but eventually times out and upon investigation, it looks like Sugar is trying to send over 100MB of data.

The record is created in Sugar - of course because the webhook is firing after update - but since the webhook fails, the subsequent call to our targets fail.

This is a known error to Sugar (since version 9) and hard to imagine that they wouldn't have addressed this break of core functionality - but they haven't.  They can't or won't recommend work-arounds and have no comment on when or if they will address the issue.

In another club discussion, someone recommended upping the limits in our MySQL to handle 100MB+ of data.  That's not a good answer for us - we don't want to send 100MB+ on every one of our transactions.

Does anyone have any suggestions - that don't involve buying third-party products - to get around this issue?  Thanks very much.

Bob

Parents Reply Children
  • Thank you very much! Sugar also offered that to me.
    I asked the question to get some more insights in sugars bug fixing policy. Sometimes bugs are silently fixed in minor releases, sometimes not.
    Yes, I can get a hotfix, but what about those who are not aware of the bug?
    When will they get the official fix? I mean the json seems to include all available php objects. It looks like a copy of your php thread memory.