Bug: Unsupported Vertex model ID error when resuming mission with glm-5.1

[jeffreyARte]

Bug Report

Error

400 {"detail":"Unsupported Vertex model ID","status":400,"title":"Bad Request","requestId":"fra1::c7rgj-1776670292120-6732d91e8f63"}

Context

• Occurs when resuming a mission (mission worker/subagent sessions)
• Model: glm-5.1 (Droid Core GLM-5.1), which is listed as a valid model on the pricing page
• The main session runs fine on glm-5.1 — this error only appears for mission worker sessions

Contradiction

The same glm-5.1 model ID works for the primary session but fails for mission subagents. This suggests mission workers route through a different backend path (Vertex AI gateway) that has a different or stale model registry.

Expected behavior

Mission workers should be able to use glm-5.1 since it is an officially listed and available model.

Environment

• Factory CLI, glm-5.1 model
• Mission resume triggers the error
• Request ID: fra1::c7rgj-1776670292120-6732d91e8f63