Issues with JSON Loss and Clay Credit Reset During Model Switch | Clay

Issues with JSON Loss and Clay Credit Reset During Model Switch

When switching from web -> offline content creation agent the JSON is lost AND the Clay Credit budget is reset. Basically someone just needs to "save" all the fields when switching between models. In some cases (e.g. offline) there are fields that DON'T exist with online agents (e.g. the system prompt) those should be cached so if I go back, I can get it back). https://cln.sh/cm66M5CP https://app.clay.com/workspaces/9621/workbooks/wb_ao7CpszCiUrh/tables/t_MdG8xFnh2D7d/views/gv_SBFiMM5eGc9Z

10 comments

Channeled
APP
·
·
We don't have specific information about JSON data loss or Clay Credit budget resets when switching between web and offline content creation agents. However, to help troubleshoot this issue, we'd need to see the exact JSON you're working with. Could you please copy and paste the JSON you're using into the chat? This will allow us to take a closer look and provide more accurate assistance with your specific situation.
Jordan C.
·
·
guys, can you not auto-close stuff?
Jordan C.
·
·
A ton of my bugs don't get responded to because AI thinks it knows the asnwer
Jordan C.
·
·
And I almost never click "talk to a person"
Jordan C.
·
·
All URLs have this problem
Mark L.
·
·
Hey Jordan, thanks for sharing this, and appreciate you following up to make sure we see it. I've logged this against a bug we have on file, and will share an update when I've got feedback on prioritization for fix!
❤️1
Mark L.
·
·
Jordan, circling back: the team has repaired the previous issue where JSON schema is lost when toggling use cases. "Clay Credit Budget" is not applicable to Claygent – more of a net-new feature request – and so is not retained / is not applicable when switching between use cases. Thanks for raising this!
Jordan C.
·
·
Mark L.
·
·
My understanding is that "Clay Credit Budget" only displays when using... - certain models (ie. Sonnet 3.5, 4o, etc.) - "Content creation/manipulation" (not Claygent) - a shared Clay key rather than a personal/company key This is distinct from the "Max Cost" field (in $ dollar terms) you might see for Claygent, when also using a higher-cost model and a personal key. I see Clay Credit Budget resetting again when clicking the Use Case menu, so will raise to our engineers. (Luckily, haven't seen similar issues with "Max Cost".)
Mark L.
·
·
Hey Jordan, quick update here. The "Clay Credit Budget" no longer resets when you click the "Use case" menu. The value is not cached when switching between them / actually selecting a different use case. We've raised that as a separate product request. But hopefully minor mis-clicks on that menu aren't as interruptive now.