AWS CDN links expiring to fast for automation

[Caleb_Hubbartt]

I have a simple automation for a Pinterest automation. Pulls records from a field as it enters a view and pushes to a google sheet. Which is then picked up and pushed out to Pinterest via IFTTT.

What I can’t figure out is why sometimes the attachment (image) URL is sent out as an AWS CDN link and sometimes it’s sent out as a dl.airtable link.

The airtable links always work.

The AWS cdn links work sometimes. More often that not I get an error that the image is no longer available. It’s the like the cdn link expires too quick for the automation. My push automation from google sheets triggers on when a new row is added so we’re talking about seconds here.

Anyone have any guidance here? This is frustrating me to no end. My automation is almost there!

[Bill_French]

Hi @Caleb_Hubbartt, and welcome to the community!

Caleb_Hubbartt:

What I can’t figure out is why sometimes the attachment (image) URL is sent out as an AWS CDN link and sometimes it’s sent out as a dl.airtable link.

I cannot attest to any of this, - just my hypothesis - I believe this is because Airtable initially creates an AWS signed URL that terminates after some unknown period and replaces it with their own CDN address. Bear in mind, there is a latency between core storage and CDN storage replicas.

In any case, I believe this issue may be related to this one.

Attachments uploaded via API vanish within seconds Importing / Exporting

Hi, I am having a problem using Integromat to upload my email attachments to Airtable. My process is to save attachments in Drive > Generate a direct download link (double checked that it works without requiring any login) > save all attachments in an array (multiple attachments) > upload the entire array to Airtable. I also get the files uploaded to Airtable as seen on my Airtable base. But within seconds, all the files vanish. I am at the end of my wits trying to figure out the problem. My …