I'm using an emulator to create orders and watching the webhook events that come through as I'm doing so. I've noticed that when I start adding items to an order, it generates an order ID with type 'UPDATE'. That's fine and expected behavior. However, when I save or pay for an order, generating an event of type 'CREATE', the order ID associated with the event is not the order ID associated with the updates. The order ID returned with the 'CREATE' event is the next order ID to be assigned instead of the one associated with the order just created.
Is this expected and typical behavior? I really want to ignore updates to an order until it is saved the first time, so I would watch for a 'CREATE' event, log the order ID as active, and watch for any changes to the order following the initial order creation. With the 'CREATE' event returning the next order ID value to be used, instead of the current order ID, this seems not possible without some workaround.
Any ideas? Thanks!