Mayato (.

Hi Seth, thank you for reaching out. Could you please share more details on how the credits were used up? In general, refunding credits is possible when the usage is caused by a confirmed technical issue on our side. That said, if something did not run as expected or did not follow your run settings, please let us know what seemed off and we will be happy to take a closer look. Thank you so much for your understanding.

Hi Will M. thank you for your patience. Happy to report that we heard back from the team and this issue should be fixed.

Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble.

Thank you for your patience as we worked on it.

Hi Will, thank you so much for sharing the loom. I can confirm the error you mentioned, and it appears to be related to the system we use for the support chat window. We will escalate this to the team and follow up with you as soon as we have an update. Sorry for the issue and thank you for your patience!

Hey there - thanks for your interest in enterprise. We want to get you routed to the right place. I will reach out to you via email for the Enterprise demo request!

Hi Loh! Good news! Happy to report that we heard back from the team and this issue should be fixed.

Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble.

Thank you for your patience as we worked on it.

Hi Loh, no committed timeline but I think it will be by tomorrow NY time as the deploy is already on pending. Thank you so much for your patience.

Hi Loh, thank you for reaching out and I am really sorry for the error. There was a bug in the AI action when using the “Create or modify content use case” with the output format set to “Fields”. Our engineers have already worked on this bug and the fix is expected to be deployed soon. If you need an immediate workaround, changing the defined output from “Fields” to “JSON scheme” should resolve the issue.

I am very sorry for the inconvenience and please let us know if you have any questions.

Hi Jon, thank you so much for sharing the Loom video, it was very helpful and I can see why the action did not work. The input field you used only accepts Salesforce field API names in the format [“id”], so Clay dynamic variables cannot be entered there. Please select the Salesforce field from the first dropdown, then choose the Clay dynamic column in the next dropdown.

I also walked through this in the gif here, please take a look and let me know if you still see the error after trying these steps. Thank you https://cln.sh/Z00t03d0

Hi Jon, thank you for reaching out, and sorry for the trouble. When I tested the Salesforce lookup record action, the Object Fields loaded instantly. It’s possible there was a temporary backend API issue at the time you tried. Could you please check again and let me know if it’s working now? Thank you.

Hi Lakshmi, thank you for reaching out. Could you please contact us at support@clay.com? We’ll need to ask a few verification questions to help recover your account login. Thank you so much.