Мониторинг работоспособности API-воркфлоу

The five minute build was genuinely fun, and that doesn't need to be justified by whether twelve people or zero people ever end up using it. Watching a webhook fire and just work is satisfying on its own. I lead product at an integration platform, so what jumps out at me here isn't the workflow count. It's whether you would know the moment one of them quietly stops doing its job, and who is actually on the hook for noticing. Most people notice when something crashes loudly. Almost nobody has a way to notice when something is technically still running but doing the wrong thing. We had an internal workflow pull a status field from a vendor's API. The vendor renamed that field in an update, and the workflow never threw a single error. It just started quietly writing blanks into a report tha…