After a Bulk Update request is approved, MX sends its updates to Google a few at a time. Everyone in the company who can open Bulk Update can follow a request and read its results; retrying and copying need a role that can create requests.
Follow the progress
Open the request in Locations → Bulk Update and go to Execute & report. Once the first update starts, a bar shows how many locations are finished, for example “12 of 40 locations finished”. A location counts as finished when all of its fields are done.
Large requests can take hours. You can leave the page and come back; the Requests list shows each request’s status. Summary keeps the creation time, the last run and the finish time.
Read the result
When every location is finished, the Result card replaces the progress. Its summary counts each outcome, and the list below it has one row per location. Filter it with Result status or search by name or address, and open a row to see each field’s result and the reason for anything not updated.
| Outcome | What happened at the location |
|---|---|
| Updated | Every field that needed a change was updated on Google. |
| Partial | Some fields were updated, others failed or were skipped. |
| Failed | No field was updated and at least one failed. |
| Skipped | Nothing was sent, for example because Google was still reviewing an earlier edit or the location wasn’t ready. |
| No change | Google already had every value you asked for. |
When locations were skipped, Why locations were skipped groups them by reason.
For a logo or cover photo, Updated means Google accepted the image. Google can still review the photo before it shows.
Retry updates Google didn’t receive
Some failures are temporary, for example when Google asked MX to slow down. For these the Result card offers a retry.
- Select Retry 3 updates; the number is how many updates can be retried.
- Select Confirm retry. A retry only resends updates Google didn’t receive, and it can’t be cancelled.
A request can be retried up to three times; the card shows how many retries are left. You can retry your own requests. Owners and Admins can also retry other members’ requests.
Send failed locations again with a new request
Other failures, such as a value Google rejected or a location Google can’t find, need a new Bulk Update request. Copy failed locations to new request creates a draft with the same values for every Failed and Partial location. Fix the problems the reasons describe, then send the copy for approval as usual.