(unless there were already something in the database with a matching combination of those 3 provided properties that constitute the unique event key). Have we discarded that case too already?
Well there shouldn’t be any build or deployment events. As I’m currently building and testing the app I have created, deleted and recreated the event source a couple of time to get all the triggering and data processing to work as expected.
I would assume that deleting an event source from a component would delete all the events associated with that source and thus would allow to “resubmit” the events if the source is added again. This works for 2 of the 5 deployments.
Currently this batch submission of builds and deployments is done after my remote receives a component link event from Compass. This because accessing the remote within the data-provider is not support, I have this post for that.
Can it be that this strange selective behaviour is related to the way the events are backfilled by my app?