Skip to main content

[Extension] How to identify the most recurring errors in your Blip chatbot with the ‘Logs and error monitoring’ extension

  • Updated

  1. Introduction

  2. How to analyze recurring errors

  3. Practical example

  4. How to validate the fix

  5. Support

 

Brief description: Use the Logs and error monitoring extension dashboard to view your chatbot’s errors in Blip grouped by recurrence, along with the number of occurrences and the trend over the last seven days.

 

Introduction

Analyzing each error manually can cause the most serious problem to get lost among isolated failures. The Logs and error monitoring extension groups identical errors into a single item and shows how many times each one occurred, so the team can immediately see what is recurring most often and prioritize fixes based on actual impact. For example, if an order lookup integration fails dozens of times a day, it appears as a single error with a high count instead of dozens of separate lines.

Before you start

Before analyzing recurring errors, make sure you have:

  • The Logs and error monitoring extension active in the bot being analyzed. Activate Logs and error monitoring in Blip Store and install it in the bot.

  • Access to the bot in the Portal.

  • Knowledge of the chatbot’s main flows, so you can identify the stage at which each error occurs.

The dashboard considers errors from the last seven days. This is the period during which records remain available before expiring.

 

How to analyze recurring errors

  1. Open the Logs and error monitoring extension in the bot’s Portal. The Error logs tab shows errors grouped by recurrence.

  2. Browse the list. Each item contains an error that repeats and displays the message, a chart for the last seven days, the total number of occurrences in the last 7 days, and the date when it last occurred.

Painel Logs de erro com os erros agrupados, gráfico de sete dias e contagem de ocorrências

  1. Click an item to expand the latest occurrence. The panel shows the user, date, bot, block where the failure occurred, execution time, action type, and input received.

When analyzing each error, pay particular attention to:

  • Which block the failure occurred in.

  • How many occurrences it has and how the chart behaves over the last seven days.

  • Whether there was a recent change to the flow before the error started increasing.

  • Whether an expected variable arrived empty in the input.

  • Whether any Builder condition is configured incorrectly.

To investigate further, click the occurrence’s debugging icon and view the details in JSON, including the input, the action settings, and the error message. If you need to take the list of affected users to another analysis, use Download CSV with impacted users.

 

Practical example

The chatbot has an order lookup flow. When opening the dashboard, the team notices that the same error in the integration stage appears with a high number of occurrences and a chart that has been rising over the last few days. It becomes clear that this is not an isolated case, but a recurring problem that needs to be prioritized. The team then reviews the integration settings, adjusts the error handling, and tests the flow again.

 

How to validate the fix

After fixing the problem, run a new test of the flow and monitor the dashboard. Check whether:

  • The error stops appearing with new occurrences.

  • The user continues the journey normally.

  • The integration returns the expected response.

  • The variables are populated.

If you want to remove the fixed item from the list, use Delete error in the occurrence. Then monitor the dashboard for a few more days to confirm that the error has not returned.

 

Support

If you have questions or encounter a problem with the extension, contact us by email at support@wiv.com.br.


 

Need more help? Explore our content on Blip Academy or Blip Community, watch tutorials on our YouTube channel or get answers to your questions through our support channel 😃