So this only sets a new tracking processor to the latest event? So if it already exists the config is ignored?
So in our case where we already started a replay we have to delete the "old" entries in the db?
Also in the example on the site o see a time. Because it is interesting for us to e.g. have the events from the last hour but not the ones 1 month ago.
I have not seen a value for the counter. Does it mean that the important part is the time? And not the blob where a counter value is in?
Because our idea by creating them manually was focusing on the counter in the blob. Not the date...