Hey team,
I have noticed that if you modify a Zap in Zapier and it get’s turned off, it removes the action from the button in Glide, even if you have turned it back on in Zapier before attempting to use it again.
This is problematic because often times you are making adjustments in a Zap after finding an error, and when you go back to the app, using the button errors out. you have to go back to the button in the editor and add the action again. if this happens with multiple Zaps, or a Zap is turned off in error, you are forced to go find that button and edit the action.
If the action would stay tied to the Zapier button and just return an error associated with a an action in Zapier that is not turned on, that would be a better option here.