I have a problem with Claygent. It may be a problem with the API, but on some occasions the output is returned correctly, but most of the time I'm getting error message. "Error message is missing in the error object. Please retry this operation." - I don't know why sometimes it works, sometimes it errors. Can anyone help?
This error typically occurs due to intermittent API processing issues. To resolve it: 1. Clear your browser cache and refresh the page 2. For Claygent specifically: • Make your search queries more specific • Break large data requests into smaller batches • Check your network connection stability Could you share the exact JSON you're using? This would help me troubleshoot any potential formatting issues that might be causing the error.
This error typically occurs due to intermittent API processing issues. Since clearing cache only worked temporarily, try: 1. Break your data requests into smaller batches (around 50 rows at a time) 2. Make your search queries more specific and well-defined 3. Check your API usage limits and quotas 4. Verify your network connection stability Could you share the exact JSON you're using? This would help me troubleshoot any potential formatting issues.
I tried only 10 requests, it's a prompt others are using, so it's fine
This error typically occurs with Claygent due to API processing issues. Since you've already tried cache clearing and smaller batches, please: 1. Check your API usage limits and quotas 2. Verify your JSON format is correct 3. Ensure your search queries are specific and well-defined 4. Check your network connection stability Could you copy and paste the exact JSON you're using into the chat? This would help me troubleshoot any formatting issues that might be causing the error.
This error typically occurs due to intermittent API processing issues. Even with a working prompt and only 10 requests, you might encounter this error due to: 1. API processing limitations 2. Network connection instability 3. Browser cache issues Since you've already tried clearing your cache with limited success, try: ** Making your search queries more specific ** Checking your API usage limits and quotas * Verifying your network connection stability Could you copy and paste the exact JSON you're using into the chat? This would help me troubleshoot any potential formatting issues.
network is good. It sometimes works sometimes not Where do I find the JSON?
{ "type": "object", "properties": { "URL": { "type": "string", "description": "" } }, "required": [ "URL" ] }
To troubleshoot your Claygent "Error message is missing in the error object" issue, you'll need to check the JSON you're using in your HTTP API requests. This JSON is typically found in the "JSON body" section when setting up your HTTP API enrichment column. Could you copy and paste your exact JSON into this chat? This would help me identify any formatting issues that might be causing the intermittent errors.
This intermittent error is likely related to API processing limitations. To resolve it: 1. Break your data requests into smaller batches (around 50 rows at a time) 2. Make your search queries more specific and well-defined 3. Check your API usage limits and quotas - this is often the root cause of intermittent errors If you're using an AI model like OpenAI or Anthropic, consider upgrading to a higher tier for better performance and fewer rate limit issues.
{ "type": "object", "properties": { "URL": { "type": "string", "description": "" } }, "required": [ "URL" ] } This is JSON
This intermittent error is likely related to API processing limitations. To resolve it: 1. Break your data requests into smaller batches (fewer than 10 rows at a time) 2. Ensure your search queries are specific and well-defined 3. Check your API usage limits and quotas - with lower tier API access, you'll need to process smaller batches 4. Try clearing your browser cache and refreshing the page 5. Verify your network connection stability Your JSON format looks valid, but the issue is likely related to API rate limits rather than your JSON structure.
it didn't help
