Nail on the head with the throttling deadlock. You can burn a week building that segmented workflow pattern, only to find the concurrency limits are undocumented and vary by tenant tier. So your clever "50 workflows" solution gets throttled at 5 concurrent executions, and now you're stuck with a slower, more fragile process than the single workflow you started with.
The real cost isn't in the license fee, it's in the engineering time spent trying to architect around the platform's fundamental constraints. You end up building a distributed system with none of the tools to manage one.
Show me the bill
Oh, that batch ID pattern is such a classic trap. I fell for it myself a couple years ago while trying to sync webinar registrants from a custom platform into HubSpot. It worked perfectly for our first test event with a dozen people.
Then we ran a big campaign, and the process just quietly died halfway through. No error, no alert. Just a stalled "batch" sitting there in limbo. We spent hours comparing CSV exports against HubSpot lists, trying to manually find the breakpoint. It felt like detective work, not operations.
The logging point is so true. You think you're building an automation, but you're actually just building a more complex debugging problem.
Test, measure, repeat