openclaw - 💡(How to fix) Fix openclaw infer embedding create fails with TypeError: fetch failed on Node 24 despite valid Voyage credential; underlying cause is swallowed [1 comments, 2 participants]

• openclaw infer embedding create --provider voyage --text 'probe' --json exits with only TypeError: fetch failed.\n- NODE_OPTIONS='--dns-result-order=ipv4first' does not change the failure.\n- OPENCLAW_DEBUG_MEMORY_EMBEDDINGS=1 does not add useful output; it still exits with only TypeError: fetch failed.\n- Gateway logs also show provider fetch failures such as OpenRouter pricing fetch failures.\n\nImportant diagnostic:\n- Passing OpenClaw runtime [email protected] Agent to Node 24 global fetch reproduces InvalidArgumentError: invalid onRequestStart method, code UND_ERR_INVALID_ARG.\n- However, the installed fetchWithSsrFGuard appears to route dispatcher calls through bundled runtime undici.fetch, and direct guarded Voyage controls succeed.\n- So the embedding CLI failure may be from a provider path that bypasses that runtime-fetch fallback, passes a custom fetchImpl, or otherwise loses the underlying cause.\n\nExpected:\n- Embedding CLI should succeed when the same key/request succeeds through direct fetch and guarded fetch.\n- If fetch fails, CLI should surface error.cause / UND_ERR_* details instead of only TypeError: fetch failed.\n\nAsk:\n- Please audit the infer embedding create / Voyage provider path for any global-fetch + runtime-dispatcher mixing or custom fetchImpl path.\n- Please preserve/log the underlying fetch cause for provider embedding failures.

TL;DR

The issue can be resolved by auditing the infer embedding create path for mixing global-fetch and runtime-dispatcher, and preserving the underlying fetch cause for provider embedding failures.

Guidance

• Review the infer embedding create code path to identify any potential mixing of global-fetch and runtime-dispatcher, which may cause the TypeError: fetch failed error.
• Check if a custom fetchImpl is being used in the Voyage provider path, which could bypass the runtime-fetch fallback and lead to the error.
• Modify the code to preserve and log the underlying fetch cause for provider embedding failures, instead of only returning a generic TypeError: fetch failed message.
• Verify that the undici Agent is being used correctly with Node 24 global fetch, and that the fetchWithSsrFGuard is routing dispatcher calls through the bundled runtime undici.fetch as expected.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue seems to be related to the interaction between the undici library and the Node 24 global fetch. The UND_ERR_INVALID_ARG error suggests that there may be an issue with the onRequestStart method. However, without more information about the code, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Audit the infer embedding create path and preserve the underlying fetch cause for provider embedding failures, as this is likely to provide more insight into the issue and allow for a more targeted fix.