This error appears when the Zoho CRM/related-Zoho product API call that should return custom-function failures instead returns HTTP 204 (No Content) or an empty 200 body while the Zoho web UI still shows failed functions. The API surface currently has no documented “function-failures” endpoint, so the client sees “no failures” even though the Failures view in the product lists real errors.[1]
What it means — concrete explanation tied to the Zoho API surface
The product’s public API does not expose the same function-failure report used by the UI; callers of attempted endpoints either hit an undocumented route or an endpoint that intentionally returns 204/empty 200 when no API-level failure feed exists. That mismatch produces an empty API response even when the UI has entries for custom-function failures or workflow-script errors.[1]
Common causes
- You called an undocumented or unsupported endpoint (no official function-failures API exists in the reference).[ ^1]
- You queried the wrong product or data center (DC) endpoint and hit a route that returns 204 for cross-DC or mismatched requests.[1]
- Your access token or scope lacks rights to view automation or functions, causing the API to suppress results.[1]
- You attempted to reuse a webhook-failures path; webhook-failures are documented but do not report custom-function failures.[1]
How to fix it
- Confirm the API reference: check Zoho’s official API docs for your product and DC to verify whether a function-failures endpoint is available. If no endpoint is documented, plan to use the UI or application logs instead.[1]
- Use the UI Failures view for immediate triage: open Zoho CRM (or the product that runs the functions) > Setup > Automation > Functions/Failures to see and re-run failed functions. Copy timestamps and function names for auditing.[1]
- If you must automate: instrument your functions to log failures to a searchable store (Zoho Analytics, a custom webhook, or an external logging service) when they catch exceptions. That gives you an API-accessible failure stream independent of the product’s internal failure viewer.
- Verify OAuth scopes and DC: confirm the OAuth client uses scopes that allow reading automation/function metadata and that your API base URL matches the org’s DC. Retry after correcting scopes or base URL.[1]
- Collect evidence and reproduce: capture the API request/response (headers, URL, body, HTTP status), the UI failure row (function name, time, error message), and the account DC. Prepare these before contacting Zoho support.[1]
When to escalate
Open a Zoho support ticket when you can reproduce the mismatch with request logs and the UI screenshot; include timestamps, request/response dumps, and the affected account/DC. Escalate if this blocks automation recovery or you need an official API for failure monitoring beyond manual UI checks.