Site crawls that fail now say so

A monthly site crawl that stalls or cannot fetch a page now ends as failed with the reason, shows that reason on the Audits page, and raises a site health alert if it keeps happening. Behind that, every agent session the platform starts is now a run with a transcript.

Most of today went into making work that fails say so, on both sides of the platform. A crawl that cannot finish now reports that it cannot finish, and an agent session that runs now leaves a record of what it did.

For our partners

Site crawls report failure. A monthly crawl that stalls partway, or that cannot fetch a single page, now ends as failed with the reason attached instead of sitting open or scoring a site on nothing.

On the campaign’s Audits page a failed crawl carries a Failed badge with the reason under it. Site health tries again on its own for a while; if the crawl still cannot finish, the campaign raises an alert that names the cause, whether the site’s robots file is turning the crawler away or the address could not be reached at all. The next crawl that finishes closes the alert.

The practical difference: a site that quietly stopped being crawled used to look the same as a site that was fine. Now it looks different.

Behind the scenes

1. Every agent session the platform starts is now a run, with a page of its own and a transcript of what it did.
2. The call review was rebuilt. A recorded meeting opens its own conversation when the recording is filed, and the agent writes to-dos and notes straight onto it.
3. Team mail now arrives the moment it lands rather than waiting for the next scheduled pass, with that pass kept as the backstop.
4. Our browser agents learned a new content system, so edits on sites built with it can go to an agent instead of a person.

1. One kind of agent session

Several kinds of session used to run with no run behind them: a review send, a flagged touchpoint, a hand-off, a mention. They did the work and left nothing you could read afterwards. All of them now open the same way, so there is one list with the record each session was working on, what it ran and what came back.

2. Call review without the confirm step

The agent that reads a meeting transcript now writes directly: to-dos with an owner, a due date and the quote they came from, product remarks where they belong, a hand-off when something needs a person. The summary lands on the recording once. The step where someone confirmed a proposed summary before any of it existed is gone, and so is the queue it sat in.