Trace topping failures with Function Logs

Trace topping failures with Function Logs

Hello everyone,

Debugging a topping issue used to mean starting from scratch, with no visibility into what its custom functions actually did or where things broke. Function Logs change that; for any topping installed in Bigin, you can now see the execution history of its underlying functions, right down to when a failure happened and why.

Here's a quick scenario

Say a customer is using the QuickBooks topping, and a few days ago, its sync quietly stopped working. This means the records from QuickBooks aren't reflecting in Bigin anymore. They reach out to support, but with no visibility into what the underlying function actually did, there's no way to tell where the failure happened.

With Function Logs, the support team can now search for that topping directly via a screen-sharing session. Any failure shows up right there-when it happened and why-giving the team enough to actually start debugging instead of guessing.

How to get started with this enhancement  

  1. Go to Settings > Toppings. Click on Function Logs at the top right corner. 

  2. Search for a topping you want to check. Click on a Function Name to see its execution history.

  3. Click the failed entry to see the details, such as when it failed and the reason for the failure.

NotesNote: Function Logs are for reference only; you can't jump from here to edit the function. Fixes still happen on the Bigin Developer Center, where toppings are actually hosted.


Editions: All paid editions
Availability: All DCs

For detailed setup instructions, refer to the help doc.