Skip to main content
When I try to run the zap and leave it on the system throws a "Pausing Zap for unknown" error and shuts down again.I would appreciate any help to resolve this issue.

Hi @Operaciones WOM 

Can you please provide more details about your Zap?

What is the trigger?

What is the action?

What Zapier plan do you have?

Perhaps provide screenshots.


@Operaciones WOM 

Here may be some helpful support articles to reference…

https://zapier.com/help/troubleshoot/behavior/zap-is-paused-and-not-running

https://zapier.com/help/troubleshoot/behavior/cant-turn-on-zap


Hi @Operaciones WOM 

Can you please provide more details about your Zap?

What is the trigger?

What is the action?

What Zapier plan do you have?

Perhaps provide screenshots.

I have a zap that sends registration updates from Jira to Google Sheets, with filters, find and informational by Slack:

 

 

When he tried to run, the zap remains on, but after a few minutes Zapier turns it off automatically. As shown in the following image:

 

 

I checked the connections, triggered the data extraction again, I tested the flow by coapiating it with a new one, but the only error it showed me after testing is the following:

and I don't know how to solve either, since I give all the permissions in Google Sheets and it has no user restrictions.

 

I really would appreciate any help to resolve this issue.


@Operaciones WOM

Check this specific article related to the error you show: https://zapier.com/help/doc/google-sheets-error-writing

Check these help articles related to GSheets: https://zapier.com/apps/google-sheets/help


 

I fixed my problem with Google Sheets, but I still can't get Zap running because Zapier automatically turns it off. I currently have no errors:

 

 

The truth is that I don't know what else to try


@Operaciones WOM I suggest you submit a ticket to Zapier Support here: https://zapier.com/app/get-help

If/Once resolved, please share the resolution here for the greater benefit of the Zapier Community.


Hi @Operaciones WOM ,

Circling back here as I see you were in touch with Support who relayed that you have encountered a known bug where the "Updated request" trigger is pulling is a response that is too large.

While we are unable to give you an ETA for a fix you have been added as a subscriber so you will receive any updates on fixes as they happen.