The first thing a HubSpot portal tells an auditor is how many HubSpot workflow errors it has. On the one we opened in September the answer was 22, out of 70 switched on. Nearly a third of the automation, failing. Our first report said as much, and it went further: both of the company’s email nurture workflows were broken, on a portal whose whole business problem was that inbound had gone quiet.
That paragraph was wrong in a way worth taking apart, because the way it was wrong is the way most people read that badge.
What was the error count actually counting?
Two things, neither of which was “broken automation.”
The 22 was a lifetime figure. HubSpot records the last execution error on every workflow, and the earliest of those reached back to 2021. Nothing on the badge distinguishes an error from four years ago from one this morning. Parsed by date, seven enabled workflows had errored in the last 30 days, two of them on the day of the audit.
The first four of the seven were property-copy loops. A workflow that copies the company name onto the primary contact had enrolled records 729,866 times, 8,634 of them in the previous seven days, in a portal with fewer than 5,000 contacts. It was erroring because it was thrashing, and it was being deleted anyway, one of 23 workflows that existed only because HubSpot cannot read a value across an association.
That left the two that mattered, the welcome sequence and the nurture sequence that follows it. Here the correction is the whole piece. HubSpot’s automation-issues view listed the welcome sequence’s errors by cause: six contacts with bounced addresses, five contacts unsubscribed from that subscription type. 1 Editor's note 1 A read-only service key cannot see the automation-issues view: the automation scope is either absent from HubSpot’s service-key catalog or not grantable on this tier, so an audit built from a key alone cannot read workflow health at all. Eleven suppressed sends. Every one of them was HubSpot doing its job, refusing to mail someone it had already learned not to mail.
Across the portal the pattern held. Of 13 issues flagged, eight were send refusals: bounced, unsubscribed, quarantined, no address on the record, an invalid address, a non-marketing contact. The other five were record writes: two that could not find their target, one copying from an empty field, one creating a record with invalid properties, and one trying to move a lifecycle stage backward. Not one was a sequence that had stopped sending to people it should have sent to.
The automation was not broken. The list was.
A badge nobody reads is how a portal decays
The distinction matters because the two diagnoses lead to different work. “Both nurture workflows are broken” sends a marketer into the workflow editor looking for a bad step. “Eleven of your welcome enrollments were bounced or opted-out addresses” sends her to the list, and it says something about every list in the portal: that addresses had been bouncing and unsubscribing for years, that the platform had been quietly absorbing it, and that the one signal it raised about this was a number in a corner of the screen that a lean marketing team had no reason to open.
Every one of them was HubSpot doing its job, refusing to mail someone it had already learned not to mail. The automation was not broken. The list was.
A badge that counts is not a monitor. It only goes up, and once the number stops meaning anything it stops being read. The errors were real. They had been filed as background by everyone who walked past them.
The second example from the same portal had no badge at all.
When we pulled the images the company’s marketing emails pointed at, 197 distinct files on HubSpot hosting, 76 of them were already gone. Every URL form returned nothing. They were not in the File Manager, not in the 30-day trash, not in the deletion history, which only reaches back to August 2026. The most-used of the missing files was the company’s own logo, referenced by 180 emails. The result: 365 of the portal’s 442 marketing emails were rendering with broken images on the day we read them, 15 of them in sends that were still automated: an account-based sequence with its A/B variants, and two surveys.
No badge. No error. A send with a dead image is a successful send as far as the platform is concerned. The company found out because an archive pull during the exit counted the 404s, not because any report in the portal did.
Read the log. Do not count it.
The lesson for anyone running a HubSpot portal, leaving or not, has two halves.
The first is about reading. The number on the badge is useless; the list behind it is not, because every row names a cause. A few minutes in the automation-issues view, sorted by date, turns “22 broken workflows” into four copy loops, eleven bounced or opted-out addresses on one sequence, a promotion mailing people who had opted out, and one stage-change rule fighting its own settings. Do that quarterly, and read it as a list of reasons rather than a score.
The second is about what the reasons are telling you. Eleven suppressed sends on a 25-enrollment welcome sequence are a list-hygiene finding wearing an automation costume. The portal was billing for 1,401 marketing contacts; 1,157 of them could be sent to. The gap is not a HubSpot problem, and it does not go away by leaving. It goes with you, into the first campaign on whatever platform comes next, unless the suppression state is loaded before the first subscriber. We have written separately about why marketable is not subscribed and about the suppression history a HubSpot export will not give you; this piece is the reason both of those are day-one requirements of the new platform rather than cleanup tasks for the second month.
What the company gets on the other side is not a lower error count. It is a different rule in the system being built to replace the portal: a failure lands in a queue a person can open and retry, and anything needing attention goes to a shared channel, not to the marketer alone. One person cannot be the monitoring system, and silence stops being the success signal. The migration guide covers where the list work sits in the sequence of a move. First.
The research is free. So is the diagnosis. 60 seconds →