How can I leverage the CAS to get the upserted timestamp, using n1ql

Hi @Carlos_Sanchez
CAS is intended to be an opaque long used solely for optimistic concurrency, so it’s not advisable to make any assumptions about how it’s generated.
It sounds like you’re mostly trying to debug where the delays are coming from at this point, e.g. whether it’s Couchbase or another component? Presumably you can timestamp when the consumer receives a given event, when it starts sending it to Couchbase, and when it receives the response?