openclaw - 💡(How to fix) Fix [Bug]: Vertex AI rejects user_id after upgrade to 2026.4.21 — "appears to contain an email address" [1 participants]

1. Observe HTTP 400 error: metadata.user_id appears to contain an email address.

TL;DR

The issue can likely be fixed by modifying the custom provider to accept the new user_id format introduced in OpenClaw 2026.4.21.

Guidance

• Verify that the custom provider is correctly configured to handle the new user_id format, which now includes a prefix (openclaw-anon-) in version 2026.4.21.
• Check the OpenClaw documentation for any updates on handling user_id in custom providers, as the change may be intentional and require adjustments on the provider side.
• Consider modifying the custom provider to strip the prefix from the user_id before sending it to Vertex AI, if the API does not support the new format.
• Test the custom provider with a manually constructed user_id in the new format to isolate the issue.

Example

No code example is provided due to the lack of specific details about the custom provider's implementation.

Notes

The exact cause of the issue is the change in user_id format between OpenClaw versions 2026.4.15 and 2026.4.21. Without more information about the custom provider and Vertex AI API, a precise solution cannot be given.

Recommendation

Apply a workaround by modifying the custom provider to handle the new user_id format, as downgrading to 2026.4.15 might not be a long-term solution and could miss out on other fixes and features introduced in later versions.