Okay here is the story!
So I created a recipe and it looked like everything was good (I put the last updated by filter to ensure that looping didn't happen). It seems everything is okay so I continue with my day and think nothing of it.
The next morning I wake up and what do you know?! I had hit my transaction limit. Apparently it used a different last updated by # than I was expecting(The app I use typically uses -1 for the user id when an API is used. Apparently the way workato did it used mine, -7). The warning email did nothing for me as it was at 3:00 in the morning.
It would be really nice if there was some sort of confirmation. Rather than an email, a "we will not continue until you verify" or something along those lines. Optional of course. But now me personally, not the company, is out 50 bucks.
Hi Jacob, sorry to hear about that! You can consider making use of Workato apps RecipeOps by Workato (previously known as Workato Admin) to do various things e.g. Get account details to retrieve available transaction count, Get recipe details to retrieve total successful job count, Stop recipe.
If you are testing out a new recipe and want to avoid excess consumption of transactions, you can build a recipe to automatically stop a recipe and send yourself an email once it reaches X number of successful jobs i.e. used up X number of transactions or when your available transaction count hits Y amount. Would this help?
Send us a ticket, we will try our best to assist you with your problem