This topic was automatically generated from Slack. You can find the original thread here.
Is there any way to debug why a HubSpot source would just stop running? It stopped on March 1st and we had no idea.
Nvm, this goes back to my bug where it will fail if there are more than 50 changes. The logs should really surface better as errors, we had no idea this source wasn’t running.
Agreed, we need better notifications for source errors like workflow errors. We’re also working on support for a built-in dead man’s switch for workflows: if a workflow fails to process an event for a defined period of time, alert me. I think that may have also helped identify the core issue here earlier.
Yes, that would be great. Or even in the events page, surface that there are errors in the logs perhaps? Otherwise it just looks like it’s not running, but in this case it is, the logs had the info we needed.
yes, source logs / errors are stored in a distinct stream that’s not surfaced in event history, but since they’re essentially a part of the workflow (when linked to a workflow), I agree from the workflow dev’s perspective, they should just be surfaced along with all other logs, and you should get notified of errors.