Custom HTTP Apollo Call Triggers Unintended API Calls | Clay

Custom HTTP Apollo Call Triggers Unintended API Calls

FYI -- I created a custom HTTP apollo call and clicked save + don't run. Then I renamed the column, and it triggered an full run, costing me 400 API calls. https://app.clay.com/workspaces/423342/workbooks/wb_2yzrNp8cphiU/tables/t_g6XNC4yqigMb/views/gv_86Vu8v5hyjg7

5 comments

Channeled
APP
·
·
When you rename a column, it can affect the dependencies and structure of your table. By default, columns are set to auto-update whenever changes are made to the table.To prevent this in the future, you should: 1. Make sure auto-update is toggled off before making column changes 2. When restructuring or renaming columns, verify your dependencies first 3. For new changes, consider filtering and running enrichments only on specific rows you want to updateThis will help you maintain better control over when your API calls are triggered and avoid unexpected runs. Sources: HTTP API with JWT Authentication - Clay University Rename, Pin, Duplicate, Delete Column
Mathew I.
·
·
Person
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Daniela D.
·
·
Hey Mathew. Thanks for reaching out. Sorry about this. I ran a number of tests in your workspace but wasn't able to replicate this issue. To confirm, did the Lookup in the Restaurant column re-run at any point after renaming the HTTP column in the table? For context, the HTTP API column depends on the full name field in that column. When dependencies are involved, any updates made to the source column can trigger updates in other columns. Let us know if the Lookup integration ran also ran. Happy to troubleshoot further.
Channeled
APP
·
·
Hi Mathew I.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: