1- Using sticky is simple. Yes. But that didn’t solve our problem. I bet it’s helpful on a lot of cases, but the problem I described was on a different request with a sensitive data that should’ve been created on the previous step.

2- I’d agree, if this was just like the sticky case, but the point of this is to only call it on sensitive data that should be present. If you performed a payment and get redirected to the next screen, they payment should be there, so that extra query on the write connection is needed. But yes, it will increase the db connection, but it’s a sensitive place, so it’s worth it.

3- You are correct. Perhaps I should clarify that this macro is only for sensitive data, and to not use on normal queries.

Thanks for the response, I hope I was clear on the difference with sticky