This topic was automatically generated from Slack. You can find the original thread here.
I think there’s something bugging with the hubspot-new-engagement trigger. I can deploy it alright, and it does send me an initial batch of old events. But I get nothing at all after that initial batch.
Looking at the source logs, the second one you linked had exceeded memory usage on one run, so it probably fetched too many objects (and hubspot objects can be pretty large). The original one seemed to be running and just not retrieving anything.
Yeah, I noticed when I deployed the dc_gzuxvel trigger that the initial sample batch I got was event dating all the way back to 2024. So my guess is that at some point more recently, HubSpot stopped logging engagements in ways that would be picked up by that endpoint, and probably moved to what that new endpoint I shared picks up. Which would explain why the trigger is running but not receiving anything.
Regarding the second dc_x2uvgpA trigger, is there a way I can spot incidents like that myself, so I can resolve it. What do I do in such scenarios?