The "Unable to process your request" message in Zoho Desk is a generic failure response that appears when the Desk UI or an embedded integration cannot complete an operation — often caused by authentication, permission, or temporary service problems. This page explains what the message means, common causes tied to Zoho APIs and integrations, and step-by-step fixes.
What it means
Zoho Desk (and related Zoho apps or gadgets) returned a failure before a specific error payload could be delivered; the platform blocked the request or the integration failed to complete its handshake. For integrations and embedded gadgets this typically means the call failed at authentication, permission checking, or routing at the service layer rather than at a Desk data-validation layer [1][5].
Common causes
- Expired or invalid OAuth token or session for the gadget/integration, causing API calls to be rejected [6][5].
- Missing module or role permissions in the Zoho product (user is not permitted to access the requested Desk resource) [2][8].
- Cross-product or gadget configuration mismatch (app/gadget enabled in Google/third party but not fully authorized inside Zoho) leading to a rejected request [1].
- Temporary service or network issue inside Zoho or the third-party host that interrupts the request before a detailed error returns [3][4].
How to fix it
- Reproduce with a single user and note exact steps: record the URL, time, user account, and the action that shows "Unable to process your request."
- Refresh credentials: reauthenticate the integration or gadget. For OAuth flows, revoke and reissue the token or re-establish the connection from the integration settings (for example, re-add the gadget in Google Apps or reconnect the OAuth connection) [1][6].
- Verify permissions: in Zoho Desk Admin > Setup (gear) > Roles and Profiles and Module Permissions, confirm the user or integration's profile has read/write access to the Desk module and any linked modules referenced by the gadget [2][8].
- Check API scopes and connection: if the request uses an API connection or Deluge invokeURL, validate the connection includes the correct scopes (for create/update actions include the specific resource scopes) and that the connection belongs to the same org/region as the target resource [6][5].
- Test with curl/Postman: call the same endpoint with the same token to capture full JSON error. If the API returns a 4xx/5xx and a JSON body, follow that error rather than the generic UI message.
- Clear caches and retry: sign out of the Zoho session, clear browser cache or try an incognito window, then sign in and retry the action. This eliminates stale session state.
- Check Zoho status and network: confirm Zoho services are operational (status.zoho.com or community posts) and that your firewall or proxy is not blocking Zoho endpoints [3][4].
When to escalate
If reauthentication and permission checks fail or API calls from Postman return 5xx server errors, open a Zoho support ticket and include the reproduced steps, request timestamps, the exact API endpoint, and a curl/Postman trace so support can inspect server logs. If the issue affects multiple users or blocks automation, escalate with the account's support plan for priority handling.
[1]: Zoho CRM Gadget community report of identical "unable to process your request" gadget failure.
[2]: Zoho People HR Help Desk permissions and access steps.
[3]: Zoho Assist troubleshooting guidance for connection and certificate failures.
[4]: Zoho Community tag pages showing service-impact reports and user posts.
[5]: Zoho Connect API community thread showing authorization failures on API calls.
[6]: Deluge/invokeURL community thread showing "Execution Failed" due to OAuth/scope/config issues.
[8]: Zoho Books community posts highlighting "You are not authorized" API responses.