Yeah, but the Stripe webhook that trigger the waitForEvent for a particular workflow instance will b
Yeah, but the Stripe webhook that trigger the waitForEvent for a particular workflow instance will by definition fire after the workflow has already started. There is no way to put the instance id into Stripe metadata, because there is no way Stripe will have this information. You can't update stripe metadata before something you don't know will happen will happen. This is the case for nearly every single instance where you would use waitFor. The thing that will trigger the waitFor will fire AFTER the workflow starts or what are you waiting for? So there is no way the external event will ever know what the instance is. Reallly the only way I can see that this can possibly work is that both the Workflow and external event that will eventually trigger the waitForEvent both use a predetermined uniqueID that is considered unique across all workflows. In that way the Workflow instance Id would be created with that uniqueId. But this is quite challenging to get right. In the case of orders, I guess you will have a unique order ID that can possibly be shared by Stripe and the Workflow, but this would have to be created by a 3rd party system, so that Stripe and the Worfklow can both know it.
