Zaps dependent on Airtable aren't working

@Troy Tessalone 

Hi Troy, thank you, taking a breath now! Should I assume that when the fix is in, all of the “waiting/scheduled zaps” will rerun properly? Also, you wouldn’t by chance have any clarity on the rollback timeline, would you?

Thank you from the bottom of my heart. 

Side note: This is my first time posting here. Is this the proper forum besides emailing Zapier support to post issues such as above?

Thank you again. I would think something like this would be posted on:

https://status.zapier.com/#incidents-list

but nope…. Oy. 

@Boguslda 

Unsure.

Zapier may post about it here, may post about it on their Status page, may Tweet about it, may send and email, etc.

Best you can do it to periodically check again to verify if the Zaps involving Airtable seem to be working as expected.

@Boguslda

Still waiting on an official reply from Zapier.

NOTE: We’ve pushed them internally to put out a reply.

I have not made any changes to any of my Zaps, because if you did, you may have to make changes again.

@Troy Tessalone 

Thanks for reaching out @Boguslda! I know not having access to necessary data definitely isn’t ideal. In digging into this it appears there was a secondary issue impacting the original rollback and some users may still be experiencing this bug. The team is actively still working on a solution for these users. In the meantime, I’ve added your email to to be notified directly once a fix is in place!

All that being said, depending on if your Zap(s) are still affected by this, this is a potential workaround to retrieve any lost data. In the interest of transparency, this will likely only work if you were part of the group who was successfully migrated.

1. Make a copy of your affected Zap(s).
2. Create a checkbox field for your Airtable records called "Send to Zapier". Then, create a new view in Airtable called "Missed Records". Set this view to only include records that have a ticked box in the "Send to Zapier" field. The new view should be empty. Do not add check the box in this new field until the Zap is set up and turned on.
3. Set the new copy of your Zap to trigger on the Missed Records view. Turn the Zap on, and try checking the box in the Send to Zapier field for one record to confirm that it enters the new Missed Records view and triggers the Zap.
4. Once you've confirmed that this works, you can check the box on the "Send to Zapier" field for all of the records that the original Zap did not process.
    

Then, you can turn this Zap off and simply allow your original Zap(s) to continue running.
 

We’ll also be sure to keep this thread updated as soon as we know more. We truly can’t thank you enough for your continued patience while the team works out a solution for this.

Some automations are coming back to life, but far from all. For example 200 negative results went out tonight (Yay) but the two POSITIVE COVID results got stuck and never fired… Hopefully all resolved by tomorrow AM.

Haha, makes me feel good I guess about being 3 for 50, LOL!

Is anyone still seeing this issue?  It seemed to be resolved last week, but as of late last night we’re seeing the “field_” nesting issue again and our zaps are hitting errors.  Refreshing fields isn’t working either.

@Buttonjer So that was exactly what I thought was happening -- the first few errors I got were indeed on Zaps that we “fixed” during the initial bugginess last week, but then I also got an error on one we had left alone (once we found this thread, we stopped messing with things and just waited for the rollback).  Weird thing is, when I try to manually fix these zaps, I still only have the fields with “Field” written before the title, so there is no option to go back to the way things were!

Just to be a good citizen, here’s the solution we found--our Test Data was outdated and was still pulling in things from Airtable that were mapped incorrectly, thus the following steps also only showed options with the “Field” prefix before the field title.  We couldn’t fix it before simply because the Zapier servers went down for a little bit right when we were trying!  The fix was as simple as pulling in new Test Data after the servers were back up.