Automation error: "An attachment url is disallowed" when run automatically
Hello everybody,
I have a weird problem with a gmail automation. When testing the automation works perfectly. The automation looks for a field value that is greater than 4 and then the actions are run.
When manually changing the a value in the record that is used for the automation to a value greater than 4 the automation also runs perfectly.
But when the automation its run automatically I suddenly get the following error in the logs:
It doesn’t make any sense that this automation suddenly throws errors when it is run automatically, but every other way of running it works fine. Also, when this same automation is run again manually it just works…
Someone any idea what’s going on?
Hi there!
Here another victim to the "failed email because file did not finish uploading" Airtable error 🙂
Great answers and I've compiled them to generate this solution: I've created a formula field that will output "Uploading" when it detects a file with the following urls: "https://cdn.filestackcontent" or "https://zapier" or it does not detect "https://dl.airtable", and will output "Uploaded" on the contrary.
Details to replicate:
1- Create a "all_documents" formula field that just concatenates all the Attachment fields you want to validate. Mine looks like this:
{PandaDoc PDF}&Attachments&{Proof of Payment}
2- Create the validation formula field. I've named mine "Documents Upload Status"
IF(all_documents!="",
IF(OR(FIND("https://cdn.filestackcontent",all_documents) > 0,
FIND("https://zapier",all_documents) > 0,
FIND("https://dl.airtable",all_documents) = 0
)
,'Uploading','Uploaded')
,"")
In the formula I've just validated against "filestackcontent" and "zapier", but if you find that other uploading urls appear in your case you should add them to the formula.
3- Use this formula as a validation before running automations that need that uploaded file(s).
Additional comments:
I tried using the "REGEX_MATCH" airtable formula to find all urls that were not identical to "https://dl.airtable" but apparently Airtable does not support negative lookahead (?!text) in regex expressions.
And here is a screenshot of how the not fully uploaded document from Zapier was breaking my Airtable automation:
