Question: Does anyone have any tips on how to avoid erroring Argon Claygent? I've already cut up the request in multiple parts, but it errors roughly 30% of the time. Issue is that my n8n workflow is dependent on the HTTP call back, which never fires because of the error. Therefore the n8n workflow times out. Any tips anyone?
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Casper clicked 'Talk with the team!'
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Hi Caspe,
Thank you for reaching out to the support team. Can you please send me a link to the table you're working on? As soon as I have that, I can dive in and troubleshoot!
Okay I'm looking into this, are you also seeing this behaviour in other tables with more rows?
For now mostly this table. It has complex Claygent requests. Maybe too complex so they time out. Not sure how to solve this
Any news Munnawar H.
I've escalated this to our engineering team to dive in a little deeper. They're US based so there'll be a little delay in getting a solution out. In the meantime, I agree with the complexity of the tasks. Could you recreate the column and try breaking down the instructions into two different columns this should increase the success rate here.
Allright thanks! Yeah might need to break them up. Probably just timing them out due to the complexity. I'll double the number of agents to make it less error prone. Thanks for now Munnawar H.!
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
