Issue: Max Cost Not Saved When Duplicating Table in Claygent

·

Hi Clay Support! When I duplicate a table, the Max cost set in Claygent for OpenAI API key usage is not saved. Please fix it. It costs a lot of money when you think that everything is how you built, and then unexpectedly check the cost and found out that it's not.

3 comments

· Sorted by Oldest

Channeled
APP
·
·
When you duplicate a table in Clay, only the sources and header structure are copied—settings like the Max cost for OpenAI API key usage are not transferred. This means any custom limits or configurations, including cost controls, must be manually set again in the duplicated table to avoid unexpected charges. To prevent this, review and reapply your Max cost and other settings after duplicating a table.
Sources: Table management settings | Documentation | Clay University Table management settings | Documentation | Clay University
Olha Vakuliuk
·
·
Makes absolutely no sense.
Channeled
APP
·
·

Channeled
APP
·
·
When you duplicate a table in Clay, only the sources and header structure are copied—settings like the Max cost for OpenAI API key usage are not transferred. This means any custom limits or configurations, including cost controls, must be manually set again in the duplicated table to avoid unexpected charges. To prevent this, review and reapply your Max cost and other settings after duplicating a table.
Sources: Table management settings | Documentation | Clay University Table management settings | Documentation | Clay University
Olha Vakuliuk
·
·
Makes absolutely no sense.
Channeled
APP
·
·