Bug Report: Data Not Transferring Between Clay Tables

Emil C. · 2025-10-20T10:25:40.756Z

Hi, I experience a bug. Data from this table (https://app.clay.com/workspaces/308271/workbooks/wb_0t2u95hpam2BahgKT6m/tables/t_0svs6q5eBB4caVaa2d2/views/gv_0svs6q5bNy9QQPdCU29) is not being sent to this table (https://app.clay.com/workspaces/308271/workbooks/wb_0t2u95hpam2BahgKT6m/tables/t_0t2u9f2c9NHHQiP5z84/views/gv_0t2u9f7ysN2vzaoRDic) - why?

Bug Report: Data Not Transferring Between Clay Tables | Clay

7 comments

· Sorted by Oldest

Kashif J.
·
·
Hi Emil,
Earlier today, AWS experienced an incident in the US-EAST-1 region that caused increased errors and latency across multiple services. AWS has since applied mitigations and is reporting significant signs of recovery, though some requests may still be processing as they work through a backlog.
You can see further details regarding the incident here:
https://health.aws.amazon.com/health/status
Based on the time you reached out, it’s highly likely the issue you experienced was related to this incident. Services should be behaving as expected on our side, however, we will continue to monitor these issues as AWS has not marked the incident as resolved. If you’re still seeing any problems, just reply to this message and we’ll be happy to help.
Additionally, our support provider Intercom was also impacted by the AWS outage. As a result, some customers experienced difficulty reaching us through in-app support. We sincerely apologize for any inconvenience this may have caused.
Thank you for your patience while this was resolved.
Emil C.
·
·
It's still not working
Kashif J.
·
·
Hey Emil, I apologize for any confusion, I initially thought the issue might have been related to the recent AWS outages. But sorry, it actually looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Emil C.
·
·
Okay, could be good. Anything I could do?
Kashif J.
·
·
Hi Emil,
I've escalated this bug to our engineering team, and they're looking into it now. You're all set, so no further action needed on your end!
Thanks so much for raising this with us and we'll keep you posted with any updates.
Kashif J.
·
·
Hi Emil,
Upon some further inspection into your workbooks, I noticed that there was a filter applied on your "(SOURCE) Propel News (Expansion) - All" table where it was only showing rows that were "Approved for sending", this was hiding some of the more recent rows in the workbook. I removed this filter to be able to see all rows, and it looks as though both tables are in fact operating as intended, and rows are being sent from "(WEBHOOK SOURCE) Pull in data from a Webhook Table" to "(SOURCE) Propel News (Expansion) - All", as intended. If there still seems to be some inconsistencies after removing the filter between the two tables, do let me know!
Bo (.
·
·
Good news! We’ve heard back from the team, and the AWS issue has been resolved. Their systems are fully operational again -- and so is our platform.
Please try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if everything’s working on your end or if you’re still seeing any issues.
Thanks for your patience while we got this sorted out.

Kashif J.
·
·
Hi Emil,
Earlier today, AWS experienced an incident in the US-EAST-1 region that caused increased errors and latency across multiple services. AWS has since applied mitigations and is reporting significant signs of recovery, though some requests may still be processing as they work through a backlog.
You can see further details regarding the incident here:
https://health.aws.amazon.com/health/status
Based on the time you reached out, it’s highly likely the issue you experienced was related to this incident. Services should be behaving as expected on our side, however, we will continue to monitor these issues as AWS has not marked the incident as resolved. If you’re still seeing any problems, just reply to this message and we’ll be happy to help.
Additionally, our support provider Intercom was also impacted by the AWS outage. As a result, some customers experienced difficulty reaching us through in-app support. We sincerely apologize for any inconvenience this may have caused.
Thank you for your patience while this was resolved.
Emil C.
·
·
It's still not working
Kashif J.
·
·
Hey Emil, I apologize for any confusion, I initially thought the issue might have been related to the recent AWS outages. But sorry, it actually looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Emil C.
·
·
Okay, could be good. Anything I could do?
Kashif J.
·
·
Hi Emil,
I've escalated this bug to our engineering team, and they're looking into it now. You're all set, so no further action needed on your end!
Thanks so much for raising this with us and we'll keep you posted with any updates.
Kashif J.
·
·
Hi Emil,
Upon some further inspection into your workbooks, I noticed that there was a filter applied on your "(SOURCE) Propel News (Expansion) - All" table where it was only showing rows that were "Approved for sending", this was hiding some of the more recent rows in the workbook. I removed this filter to be able to see all rows, and it looks as though both tables are in fact operating as intended, and rows are being sent from "(WEBHOOK SOURCE) Pull in data from a Webhook Table" to "(SOURCE) Propel News (Expansion) - All", as intended. If there still seems to be some inconsistencies after removing the filter between the two tables, do let me know!
Bo (.
·
·
Good news! We’ve heard back from the team, and the AWS issue has been resolved. Their systems are fully operational again -- and so is our platform.
Please try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if everything’s working on your end or if you’re still seeing any issues.
Thanks for your patience while we got this sorted out.