When an item is published, Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends…
You see how your 1000 operations get used up in a minute now? Each scenario run is 2 operations, so it only needed 500 loops to use the entire quota.
The issue is a circular event feedback loop - your scenario causes an action to be made that causes Webflow to re-trigger your scenario.
To avoid this, you need to uncheck the “listen to” CMS-related events in the Webflow connection itself.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Did you know, the concepts of about 70% of questions asked on this forum are already covered in the Make Academy. Investing some effort into it will save you lots of time and frustration using Make later!