Sudden increase of operation used

What are you trying to achieve?

Hi,
I have a problem with quantity of the operation. All last year I was comfortably within the 120K limit per year. This year, after 4 months, the limit was exceeded. Nothing has actually changed, neither the time between scenario launches nor the output quantities. So what could have happened?

For example 150 lead is 1500 operations !!!

Steps taken so far

  • I checked how often scripts are checked and it is 30 minutes, or even an hour in the case of one
  • Could email address verification be the reason?
  • I checked the forum and one topic would even match, but the solution was private

Welcome to the Make community!

I would suggest completing the Make Academy before jumping into building a complete scenario. If you need specific assistance when you are building a scenario it’s easier to help you then. Otherwise, you can also hire a professional by posting a request in the Hire a Pro category.

Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —

Getting Started

Help Centre Basics

Articles & Videos

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Let’s see a sample run of one of your successful scenarios? And the schedule for it.

I think that was the matter of e-mail validation, I’ve change it to: [1]+@[a-zA-Z0-9.-]+.[a-zA-Z]{2,}$ and operations multiples, Then I’ve deactivate validation and it’s back to regular. Now Scenario is crash because of validation but at least I have a clue


  1. a-zA-Z0-9._%± ↩︎

Validation or parsing out elements? If you were parsing I could see how it would parse out more elements but validation should not have created more operations.

It was validation. I’ll try with different aproach to import contacts to Mautic. Thanks thou for answer.