Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi, everyone! How are you doing?

I work with a Zapier that has already been published with integration between posts in Slack and a spreadsheet in Sheets (job creation in the spreadsheet).

However, for some reason, the jobs were being entered up to the date of 05/07/2024. The jobs created today in Slack are not being entered in the spreadsheet.

I did a test and realized that this only works for new jobs; the old ones enter the spreadsheet normally.

Reviewing the Zapier, the only thing different I found was a message about a possible loop detected. However, I have no idea what is causing the loop and if that is why the jobs are not being created in the spreadsheet via integration.

Can you help me, please?

 

Hi ​@enzo.berardo 

The warning about a Zap loop detected is because you have Slack as the trigger step and Slack as a Zap action step.

Depending on how the Zap is configured, the Slack Zap action step (in theory) could fire the Slack Zap trigger step, thus creating an infinite loop that only stops once your Zap turns OFF or you run out of Tasks to use.

If the Slack Zap trigger channel is different from the Slack Zap action step, then the warning is merely that, a “warning” for you to be aware of.

In the warning, click the link to see more info.

 

Hey there, ​@enzo.berardo 👋

Just came across this and wanted to check how you’re getting on. There were a couple of incidents reported for Slack triggers around the time you posted that were since resolved:

ea90671edad4d99cdf5e0a65c013174d.png

I expect those might have been what was causing the issues here. Did Zap start working again after the fix was rolled out, or are you still experiencing issues?

Let us know whether you still need any help at all, want to make sure you’re all set! 🙂

Terms & Conditions