The service is taking longer than expected. Try again later.

@Nagaraju Alladi

Yes, this error can occur when Agentforce Coworker is enabled but the required configuration or access is not fully set up.

I would recommend checking the following:

1. Verify Agentforce setup
   • Go to Setup → Agentforce and confirm that the Agentforce Coworker is properly enabled and activated.
   • Check that the required Agentforce features and related settings are enabled in the sandbox.
2. Check user permissions
   • Make sure the user has the required permissions for Agentforce/Coworker and access to the objects and fields being queried.
   • Also verify that the user's profile or permission sets provide the required Einstein/Agentforce permissions.
3. Check Data Cloud / Data 360 configuration
   • If the Coworker is using Data Cloud/Data 360 data, verify that the required data sources, data spaces, and permissions are configured correctly.
   • Make sure the data being queried is available and accessible to the Agentforce user.
4. Test with a very simple prompt
   • Try a basic prompt such as:  
     What is today's date?

   • If even a simple prompt returns "The service is taking longer than expected. Try again later.", the issue is more likely related to the Agentforce configuration, org permissions, or the Salesforce service rather than the query itself.
5. Check Debug Logs / Agentforce monitoring
   • Review the Agentforce/Einstein logs and browser console for additional error details.
   • If available in the org, check the Agentforce session or interaction details to identify where the request is failing.
6. Check Salesforce Trust
   • Since this is a service-timeout type of message, also check Salesforce Trust for any incident affecting Agentforce, Einstein, Data Cloud, or the relevant sandbox instance.

If all configuration and permissions look correct, try disabling and re-enabling the relevant Agentforce feature in the sandbox, then test again. If the issue continues with even basic prompts, I would recommend opening a Salesforce Support case and providing the Org ID, timestamp of the failure, exact prompt, and screenshots/error details.

The important point is that this message by itself doesn't identify the root cause; checking the Agentforce configuration, permissions, logs, and Salesforce service status should narrow it down.