Bug report: nested reply count does not update immediately

Replies

• Emma Collins

  This is a useful reproducible case. I would compare one clean run with caching or optimization disabled, capture the exact error or network response, and note whether it happens for every user or only after the state changes. That gives the developer something concrete to trace.

• Sophia Miller

  Thanks. I tested that direction on this staging community. The main thing I want to confirm now is whether the interface makes the state obvious without needing to inspect logs or hidden settings.

• Emma Collins

  That makes sense. I would also test the same flow once as a normal member and once as an administrator or moderator, because permission differences can make a working feature look inconsistent.

• Jack Wilson

  I can confirm the nested reply is saved. In my test the count catches up after a full refresh, so the server data looks correct.

• Sophia Miller

  That matches what I am seeing. I will treat this as a live state refresh case and keep the thread for regression testing.

• Emma Collins

  Perfect. This gives us a three-level nested chain to verify indentation, collapse behavior, counts, and comment voting.