Error with Airtable Trigger

Hi, ETIMEDOUT is a network issue, so it's not something that can be addressed from the callin.io side. Could there possibly be a proxy, firewall, or another component in your network causing this problem?

That said, is this causing any issues with actually fetching data? Are any rows being missed when the trigger runs next time? If so, we would likely need to update the node so it doesn’t store the last execution timestamp for failed executions.

I encountered a similar problem a few days ago that persisted for several hours. All of my workflows that were triggered by Airtable ceased to function, displaying this error.

Since the issue resolved on its own after some time, I surmised it might have been a transient issue on Airtable's side.

That's certainly another possibility I hadn't considered. If they experienced an outage, that could easily explain the issue. Thanks for helping out with this!

This is quite peculiar.

I don't recall making any adjustments to the firewall, and this workflow was functioning correctly until about one or two weeks ago.

What's even stranger is that the workflow is scheduled to run every 10 minutes, but as you can see in the image, the error isn't occurring on every single execution; it's happening intermittently. I'm still trying to figure out the reason why!

My assumption is that an issue with my internal firewall would typically result in an error on every execution, not just on occasion.

image1452×888 78.1 KB

image1432×692 63.4 KB

Any other suggestions? I've considered migrating to a different database due to the frustration this error is causing, but I need to retain these records in Airtable.
How can I resolve this issue?

Hey,

Are you still encountering the timed out message on those executions?

Please provide the rewritten markdown content *it should be in the markdown format.

Yes, that's correct. The last three timeouts occurred at 18:22, 18:32, and 20:52. Do I need to make any updates?

Hello,

You shouldn't need to update anything. A timeout typically indicates a network issue, either with your network or with Airtable. The only suggestion I can offer is to monitor your network for any drops and perhaps check with Airtable to see if that is related to one of their IPs.

Are you referring to this IP address: 54.198.105.37?

Hey,

That is correct. What's happening is callin.io is attempting to connect to 54.198.105.37 on port 443 (HTTPS assumed), but the connection is timing out.

Hi there and to the callin.io team,

I'm still encountering this intermittent issue.

Now I'm seeing a different problem... could you offer any insights to help me resolve it?

{
"context":
{
},
"name":
"NodeApiError",
"cause":
{
"message":
"certificate has expired",
"name":
"Error",
"stack":
"Error: certificate has expired at TLSSocket.onConnectSecure (node:_tls_wrap:1535:34) at TLSSocket.emit (node:events:513:28) at TLSSocket.emit (node:domain:489:12) at TLSSocket._finishInit (node:_tls_wrap:949:8) at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:730:12)",
"code":
"CERT_HAS_EXPIRED"
},
"timestamp":
1665979226409,
"message":
"UNKNOWN ERROR - check the detailed error for more information",
"node":
{
"parameters":
{
"pollTimes":
{...}, // 1 items
"baseId":
"appHNRyUb8TZqHgsL",
"tableId":
"tblCoX6hLc9cNUskM",
"triggerField":
"Last modified",
"downloadAttachments":
false,
"additionalFields":
{...} // 1 items
},
"name":
"Airtable Trigger",
"type":
"n8n-nodes-base.airtableTrigger",
"typeVersion":
1,
"position":
[
140,
560
],
"notesInFlow":
true,
"id":
"8a66bb22-73c6-4956-81b4-0ba2ce6f5fac",
"retryOnFail":
true,
"waitBetweenTries":
5000,
"maxTries":
5,
"credentials":
{
"airtableApi":
{...} // 2 items
},
"notes":
"Recupera los registros modificados recientemente de EntradasWEB"
},
"httpCode":
"CERT_HAS_EXPIRED",
"description":
"certificate has expired"
}

Hello,

That message indicating the SSL/TLS certificate has expired on the other service seems unusual and is unlikely to occur with Airtable.

Upon a brief investigation, it appears that 54.198.105.37 is an AWS service with an expired control plane certificate. While Airtable's API IP addresses don't typically include this, I suspect your NAS might have cached an outdated IP address that has since been decommissioned, potentially causing the intermittent problems you're experiencing.

Thanks again for your support, I’m not aware of any caching configuration that I've intentionally set up.

In fact, I'm unsure how to proceed with this... the certificate for the service is working and active until next month.

Everything is functioning correctly when testing the workflow or for other workflows updating Airtable data using the same API connection to Airtable.

What would you do in my situation?

Hey,

The certificate didn't appear to be for synology.me; it was a general AWS one. I suspect if the NAS is caching DNS, it would just be something it does, so it could be worth checking if there are any DNS options on it that you can adjust.

Yes!
I have some manual DNS (google ones 8.8.8.8 // 8.8.4.4)
Now I change from manual to auto… will tell you about it.