Okay, a bit of context for clarity.
I have a base that I am using for tracking inventory. We send out the packages of items. Sometimes we have some of the items in stock, and sometimes we need to order more before the package is sent.
I am using an interface that lets the end user select the items that they want to add to the package. Then they have the option to click a button to trigger an automation.
The automation looks in the table and finds all items with a check box. Then, using a repeating group, it send the relvant infromation for each item to Make via a webhook. Make then checks to see if the qty needed is less than or equal to the qty in inventory. If it is, Make creates a new record in an Inventory Change Log table to remove that qty of items from the Inventory table. The problem I am facing is if two items with the same name are sent at the same time, the webhooks are sent to make faster than make can process through them.
For instance:
Say I have 1 trashcan left in stock. If two orders are places at the same time, or really close to each other, than things go wrong. the first order that comes in will befine, the data will show that we have 1 in stock and the order was for 1. It will proess and update the inventory. But the second order will have been sent to make at the same time. So it will also show that we have 1 in stock. So Make will create two records in the change log that -1 from inventory.
What I need to happen is that Airtable will send one webhook, then wait for Make to processes that data before it moves on to the next item in the repeating group.
I hope that all makes sense. If yall have any ideas or insight, that would be great! I can provide more information if needed.!
