Claygent may be experiencing temporary processing delays rather than being completely down. This could be due to "cold starts" where serverless code experiences latency when not frequently used.
To resolve this issue:
1. Try performing a hard refresh in your browser:
• Mac: Command (⌘) + Shift + R
• Windows: Ctrl + Shift + R
2. Clear your browser cache to resolve persistent error messages.
3. Check if your search queries are specific and well-defined.
4. Consider breaking large data requests into smaller batches.
5. Monitor your usage limits and API quotas to ensure you haven't exceeded them.
If these steps don't resolve the issue, please request human assistance by clicking on "Talk to a person."
Hey Aaron, sorry about this. It looks like we’ve got a bug and I’ve flagged it to our engineering team. In the meantime, try creating a new column (not duplicate)—that’s been resolving the issue for others. Let me know if that works.
.png){kind=logo}
