First time route sync on brand new RMI project failed (route_status table not found)

[tringuyen-yw]

We have been notified that our RMI project application was enabled. We were given the source Bigquery RMI dataset and created the Bigquery linked dataset prp-poc-gcp-rmi:prp_rmi in our GCP project. We then began to create RMI routes using the route-registration-tool from this repo.

Here is the procedure

• Deployed the Route Registration Tool in Cloud Run in our same GCP project prp-poc-gcp-rmi
https://route-registration-tool-22blabla12.northamerica-northeast2.run.app/

• Granted the route-registration-sa Service Account the following roles:

  • roles/browser
  • roles/roads.roadsSelectionAdmin
  • roles/bigquery.jobUser
  • roles/bigquery.dataEditor

• Enabled roads.googleapis.com in our GCP project

• Using our self-hosted route registration tool, we imported the route project we created on 2026-03-16 using the hosted version of the tool https://goo.gle/route-selection-tool. All the 178 routes seems to be imported OK.

• Clicking on "Sync Routes" (top screenshot) we got the following error

Sync failed: BigQuery sync failed: 404 Not found:
Table prp-poc-gcp-rmi:prp_rmi.routes_status was not found in location US;
reason: notFound, message: Not found: Table prp-poc-gcp-rmi:prp_rmi.routes_status
was not found in location US Location: US Job ID: 13052a45-f1a3-498a-958d-4d55bff7a6a7

• Verified in our linked dataset, we confirm the prp_rmi.routes_status doesn't exist

HOWEVER, when clicking on the sync icon beside each route in the project side bar. The individual route sync is successful (bottom screenshot). After about an hour, we do get records in both the recent_roads_data and historical_travel_time tables.

We did the individual route sync for about 10 routes. Then somehow, the route_status table is created. We don't know if that table was created by the app itself or by someone from RMI team by coincidence. Nevertheless, the batch sync via the "Sync Routes" button now works.

[n0531m]

Your RMI dataset (linked dataset as a result of subscribing the AnalyticsHub Listing) is read only and cannot be edited/modified.

RMI updates these table in batch. When you had successfully created routes (SelectedRoutes) through the API, it was reflected the internal configuration but not to these BigQuery tables yet. The waittime was due to the batch interval and working as intended.

[tringuyen-yw]

As an end user, I don't know this hidden business logic. It would be more helpful if the app displays a suggestion to workaround the error such as "please create a route, sync individually, wait an hour, then you can use this Sync Routes function".

However, I think a more robust design would be to decouple the dependency if this RMI Road Registration Tool on the RMI backend on the presence of this route_status table. The RMI backend just needs to create that route_status table as an empty table as part of its bootstrap initialization. Because sooner or later this table must exist in anyway.

Can you relay this suggestion to the RMI backend team?