How much of your time making Switch flows is spent testing? Probably quite a lot if you’re building more complex workflows. This is time-consuming for most flows, with the deactivating the flow, finding test jobs, dragging them on Switch, reactivating… And if your flow is more complex, and especially if it’s part of a multi-flow setup, it becomes even more challenging, because often you can’t test one flow in isolation as it will expect jobs to already have private data defined, or datasets attached, or email addresses present, and so on.
Buggy provides three apps (Buggy Input, Buggy Reporting and Buggy Reception) to help with this process and make the development, test, correct cycle as short as possible. The apps help with injecting test jobs into the flow (with all metadata properly setup), helps with cleaning up result files so you don't stare at old data, and provides insight into jobs at the end of the flow (or anywhere in the middle).
The apps have been developed to be very flexible and low impact. In fact, you could easily leave them in your flows to switch them on (pun fully intended) when they are needed for some testing or debugging.