Vertex AI feature online store failed error "InvalidArgument: feature view sync not configured"

TL;DR

Create a sync config on the feature view, with a schedule or an explicit sync trigger, and point the view at its BigQuery source, because a feature view with no sync configured has nothing to serve online and Vertex rejects the serving setup until one exists. Start with the Vertex AI feature view settings and its sync configuration, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Vertex AI feature online store failed error "InvalidArgument: feature view sync not configured"

Use this when

• You see this exact message or symptom: Vertex AI feature online store failed error "InvalidArgument: feature view sync not configured"
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Vertex AI feature view settings and its sync configuration, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the feature view in the online store, its source table or feature group, and the sync config section which will be empty. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Create a sync config on the feature view, with a schedule or an explicit sync trigger, and point the view at its BigQuery source, because a feature view with no sync configured has nothing to serve online and Vertex rejects the serving setup until one exists. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the online and offline values for that entity agree
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Vertex AI feature online store failed error "InvalidArgument: feature view sync not configured"

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Vertex AI Feature Store (optimized online stores), BigQuery sources, feature views and feature groups.

Why it happens

Feature views created through the API or a script often skip the sync step that the console walks you through. Without sync, no data moves from the source into the online store, so the view exists on paper but serving it is invalid.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstG4gv6jSgccntxGIwz-13A