Debugging actions: a walk in the park

Building powerful applications is an exciting process, but let’s face it — debugging isn’t always easy. For too long, builders have struggled with inefficient and time-consuming debugging workflows. The challenge of adding multiple log steps after every action has made troubleshooting an annoying, often frustrating activity.

We’re very happy to introduce the new Action Debug Logging-feature — a game-changing tool that makes debugging your actions easier, faster, and smarter.

Changing your debugging game

Previously, users needed to add multiple log steps to be able to see where it went wrong. Decrypting unclear error messages and finding your way to the right place to find the problem was a very time-consuming task which could take hours to find the problem.

The new debug logging feature enables users to log a whole action at once, just with a simple toggle. On the renewed logs all action steps are grouped by action level, enabling users to see comprehensive logs for entire actions rather than individual log steps. This significantly reduces the time and effort required during the building and debugging actions, as builders no longer need to manually implement logging for each step. Instead, they can rely on a combined view, improving efficiency and clarity in the development of your actions.

Ease of use is key

Since debugging an action can be challenging, we've incorporated valuable feedback from our builders to improve the usability. We've implemented several ease-of-use features, including improved error messages, advanced filter options on the log page, and direct links to the exact locations where errors occur. These improvements make the debugging process more intuitive and efficient, helping you resolve issues faster and with greater confidence. 

How It Works

• 1. Enable logging at the action settings
     • In the Betty Blocks platform, you can now enable logging for an entire action. This automatically captures all steps within the action without the need for individual log configurations.
  2. View the logs
     • Once logging is enabled, you can access a detailed overview of the action's execution. Each step is logged and grouped, providing an easy-to-navigate log history.
  3. The use of log steps
     
     • The regular log steps are still a good alternative to track critical points in your actions in addition to the new feature. So, when the logging is disabled, the log steps still provide you information on performance of your actions.

Visit the documentation of this feature for more information.

The benefits for builders

1. Time-saving 
   • Builders can now focus more on building and less on debugging setup. By logging the whole action, the need to insert multiple log steps is removed, saving precious time during development.
2. Simplified logs overview
   • With all steps grouped and logged at the action level, debugging becomes straightforward. You can easily track the flow of the action and pinpoint issues without sifting through individual logs.
3. Enhanced workflow clarity
   • The grouped logging overview provides a clear and organized view of the action's execution. This makes it easier to understand the action flow and identify any potential bottlenecks or errors.
4. Faster resolution of production issues
   • Easily enable logging for an action in production to quickly identify and fix problems within your live application.

Start experiencing the new debug logging

This feature is live now and ready to be used. Head over to your application, check out logging your whole action and the renewed logs page, and experience the ease debugging your actions.

Let us know what you think! As always, your feedback helps us continue to improve and innovate. Stay tuned for more updates, and happy building!