Issue with HG Insights Performance in the Last 24 Hours

·

Team, I can't get HG Insights to run for the last 24 hours. Is there an issue?

· Sorted by Oldest

Clay
APP
·
·
Try these troubleshooting steps for HG Insights not running: Force restart the enrichment: ** Click the HG Insights column header ** Hover over "Run column" in the dropdown ** Select "Force" to jump start the run Alternative fixes: ** Double-click the stuck row and click "re-run this cell" ** Try a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) ** Clear your browser cache and refresh These steps help recover cells stuck in queued states due to performance issues.
Clay
APP
·
·
Hello! We've identified a bug related to this issue and our engineering team is actively working on a solution. The error occurs when the employee range is included in either the source or signal. You can continue monitoring the status at: https://rootly.com/teams/clay/status-pages/clay-status/public
Clay
APP
·
·
Hello! The issue seems to have been resolved now. You can re-run the source/signal and that should fix the error. Do reach out again if the issue still persists. Thank you and have a great day ahead! :)
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

Clay
APP
·
·
Try these troubleshooting steps for HG Insights not running: Force restart the enrichment: ** Click the HG Insights column header ** Hover over "Run column" in the dropdown ** Select "Force" to jump start the run Alternative fixes: ** Double-click the stuck row and click "re-run this cell" ** Try a hard refresh: Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) ** Clear your browser cache and refresh These steps help recover cells stuck in queued states due to performance issues.
Clay
APP
·
·
Hello! We've identified a bug related to this issue and our engineering team is actively working on a solution. The error occurs when the employee range is included in either the source or signal. You can continue monitoring the status at: https://rootly.com/teams/clay/status-pages/clay-status/public
Clay
APP
·
·
Hello! The issue seems to have been resolved now. You can re-run the source/signal and that should fix the error. Do reach out again if the issue still persists. Thank you and have a great day ahead! :)
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.