Assist with HTTP Node Running Multiple Times Unexpectedly

I need help with an HTTP node. It’s running multiple times inexplicably when I’d only expect it to run once based on teh configuration of the table. The graph shows several lines into the HTTP node but they should be blocked by the run condition on the node.

16 comments

Channeled
APP
·
·
There could be a few reasons why your HTTP node is running multiple times despite the run condition: 1. Check your auto-update settings. By default, columns update whenever you add a new row. If you don't want this, toggle off auto-update in the column settings. 2. Ensure your run condition is set correctly. You might need to adjust it to be more specific. For example, you could set it to run only if a certain field has a specific value. 3. If the issue persists, try toggling the auto-update off and on again, then accept the run prompt. This should update all rows. If you're still experiencing issues, please copy and paste your JSON configuration into the chat so we can troubleshoot further.
Source: HTTP API integration overview | Documentation | Clay University
Chris S.
·
·
How do I paste my json config here?
Chris S.
·
·
None of those steps worked
Channeled
APP
·
·
To troubleshoot your JSON configuration, simply copy your entire JSON and paste it directly into this chat. Once you've done that, we can help identify and fix any formatting issues. Common problems include missing quotes around keys, extra commas, or incorrect data types. If you're seeing a "failed to parse body" error, pasting your JSON here will allow us to spot and correct the issue.
Source: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Chris S.
·
·
https://app.clay.com/workspaces/206908/workbooks/wb_tgXagsXvKs4c/tables/t_4NjCr6A2Cjsf/views/gv_sHmxgMdCGP99
Chris S.
·
·
Here is the URL. Which JSON config are you referring to?
Bo (.
·
·
Hey Christopher - Which rows did you notice ended up running when they shouldn't have? Can you let me know some row numbers?
Chris S.
·
·
It’s the HTTP API call on the AT PrePro table
Chris S.
·
·
It’s running 2x every time
Chris S.
·
·
with about 3 seconds in between calls
Bo (.
·
·
That would be because there are multiple instances of the same variation inside the table. I'd recommend adding the email as a column and turning on auto-dedupe on those rows.
(370 kB)
Chris S.
·
·
De-duping isn’t the issue here. I deliberately ran a few of these consecutively for testing purposes. The issue is when the table gets to the HTTP enrichment it’s pushing twice to the downstream API instead of once for every single record.
Bo (.
·
·
Just to confirm – If records are sent twice, that means that John Enoh was sent the message 4 times (since his name appears twice), and Abhimanyu would have received it 10 times (as his name appears five times). Is that correct?
👍1
Chris S.
·
·
Yes that’s right
Bo (.
·
·
I've looked into your table on the back end and can't notice any issues. Would it be possible for you to record a video showing this behavior, especially where you're seeing it running twice? What would be helpful is to see the Clay Table side by side with the place where you're counting the duplicate runs, so we can identify if there's any action in the Clay Table that we might be missing.
Channeled
APP
·
·