Issues with HTTP API Step in Octave: Troubleshooting Tips

Bálint S. · 2025-08-20T08:48:48.514Z

I am using a HTTP API step to query Octave and generate email copy. I've ran it and it produced results for about 10% of the rows and stopped. And whenever I try to start again it does nothing. I can confirm that we have plenty of credits to use in Octave. And we are using the recommended rate limit. Is there any problem I am not aware of? How can I run all rows successfully?

Issues with HTTP API Step in Octave: Troubleshooting Tips | Clay

10 comments

· Sorted by Oldest

Clay
APP
·
·
To run the remaining rows, right-click your HTTP API column and select "Run All Rows that haven't run or have errors". This will process only the rows that failed or didn't complete, avoiding duplicate runs. If the column still won't run, try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to resolve any queued status issues. Rate limits can cause partial runs even with proper settings - our system implements retries and smarter pacing to handle this automatically. Could you copy and paste your JSON request body into the chat? This will help troubleshoot any formatting issues that might be causing the problem.
Sources: Run Options HTTP API with JWT authentication | Documentation | Clay University
Bálint S.
·
·
I wish it did. But no. I've trying running that many times. It does not progress the remaining rows. Even if I just click on the "Click to run" on individual cells it still does not do it's job. And it does not give me any error codes either. It just hangs indefinitely (See screenshot). and if I refresh the page it returns to an empty cell.
Bálint S.
·
·
there you go: https://app.clay.com/workspaces/546708/workbooks/wb_0t11exbe9djzSjj7YUU/tables/t_0t11fzxTkx6tvSiNmMa/views/gv_0t11fzy4Z7dKVK5awcG
Aditi S.
·
·
Hi Bálint - thanks so much for reaching out. Taking a look here to see what going on.
Aditi S.
·
·
Thanks for your patience as we worked through this. A few things to try right away: 1. Double-check that your Octave API key is still valid and active on your end 1. Even with Clay’s recommended rate limits, Octave may enforce stricter limits behind the scenes. If possible, reduce the rate limit further or add delays between requests. If none of those resolve it, a good workaround is to recreate the HTTP API column, with the same settings and re enter your API Key- that often pushes through the remaining rows.
Since your column consistently stops around 10% and won’t restart, this may point to a Clay-side processing issue rather than Octave itself. If the above steps don’t work, I’ll escalate this as a bug to our engineering team for further investigation.
Aditi S.
·
·
Appreciate you sharing the context here - will take a closer look to see what's happening here. As a note, I would recommend not sharing API Keys generally, especially via Slack in the future. I've gone in and deleted that message with the image, but just wanted to note that for you too
Bálint S.
·
·
wait. I understand it now I think. The ones that don't run don't have the Company table data in the 3rd row. And the HTTP API column requires something from that. It's weird that it does not show an error for it. Or even why that company table is not fully ran for all rows since the Find people step is set up to use that table (I would assume since it generates the contacts from that table it should have run for all rows)
Aditi S.
·
·
Ah! Good catch - that makes sense that it won't run if outputs from that are required. Agreed that it should've surfaced that faster so we could identify the issue easier - I'll flag this for the product team as feedback. I see that now the API seems to be working as expected?
Bálint S.
·
·
yeah that generates results now. Damn, took me ages to find something this simple 🙂
Aditi S.
·
·
Sorry for not spotting that earlier, but happy that it is now fixed

Clay
APP
·
·
To run the remaining rows, right-click your HTTP API column and select "Run All Rows that haven't run or have errors". This will process only the rows that failed or didn't complete, avoiding duplicate runs. If the column still won't run, try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to resolve any queued status issues. Rate limits can cause partial runs even with proper settings - our system implements retries and smarter pacing to handle this automatically. Could you copy and paste your JSON request body into the chat? This will help troubleshoot any formatting issues that might be causing the problem.
Sources: Run Options HTTP API with JWT authentication | Documentation | Clay University
Bálint S.
·
·
I wish it did. But no. I've trying running that many times. It does not progress the remaining rows. Even if I just click on the "Click to run" on individual cells it still does not do it's job. And it does not give me any error codes either. It just hangs indefinitely (See screenshot). and if I refresh the page it returns to an empty cell.
Bálint S.
·
·
there you go: https://app.clay.com/workspaces/546708/workbooks/wb_0t11exbe9djzSjj7YUU/tables/t_0t11fzxTkx6tvSiNmMa/views/gv_0t11fzy4Z7dKVK5awcG
Aditi S.
·
·
Hi Bálint - thanks so much for reaching out. Taking a look here to see what going on.
Aditi S.
·
·
Thanks for your patience as we worked through this. A few things to try right away: 1. Double-check that your Octave API key is still valid and active on your end 1. Even with Clay’s recommended rate limits, Octave may enforce stricter limits behind the scenes. If possible, reduce the rate limit further or add delays between requests. If none of those resolve it, a good workaround is to recreate the HTTP API column, with the same settings and re enter your API Key- that often pushes through the remaining rows.
Since your column consistently stops around 10% and won’t restart, this may point to a Clay-side processing issue rather than Octave itself. If the above steps don’t work, I’ll escalate this as a bug to our engineering team for further investigation.
Aditi S.
·
·
Appreciate you sharing the context here - will take a closer look to see what's happening here. As a note, I would recommend not sharing API Keys generally, especially via Slack in the future. I've gone in and deleted that message with the image, but just wanted to note that for you too
Bálint S.
·
·
wait. I understand it now I think. The ones that don't run don't have the Company table data in the 3rd row. And the HTTP API column requires something from that. It's weird that it does not show an error for it. Or even why that company table is not fully ran for all rows since the Find people step is set up to use that table (I would assume since it generates the contacts from that table it should have run for all rows)
Aditi S.
·
·
Ah! Good catch - that makes sense that it won't run if outputs from that are required. Agreed that it should've surfaced that faster so we could identify the issue easier - I'll flag this for the product team as feedback. I see that now the API seems to be working as expected?
Bálint S.
·
·
yeah that generates results now. Damn, took me ages to find something this simple 🙂
Aditi S.
·
·
Sorry for not spotting that earlier, but happy that it is now fixed