Thanks Christian but we figured this out - issue was off-target effects from a caching plugin meant for much more basic use cases! Appreciate the follow up.