You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a moderator clicks on the button, it changes from Yo me ocupo to Mejor no me ocupo. However, since there's a time limit (currently set on Domain at 45 minutes), the button will still show Mejor no me ocupo even if more time has passed. Then, when clicking on Mejor no me ocupo, it'll show the Te vas a ocupar de esta consulta toast, because the backend is updated but the view isn't. The button stays desynced untill the page is refreshed.
A possible solution is not allowing any actions if 45 minutes have passed since the page was loaded (this would have to be done on JS). In any case it's probably a good idea since after such amount of time there might be new comments, the discussion could have changed status, someone else might be in charge now anyway, etc.
This is not urgent and probably won't happen very often, but I thought I'd leave it documented.
The text was updated successfully, but these errors were encountered:
When a moderator clicks on the button, it changes from
Yo me ocupo
toMejor no me ocupo
. However, since there's a time limit (currently set on Domain at 45 minutes), the button will still showMejor no me ocupo
even if more time has passed. Then, when clicking onMejor no me ocupo
, it'll show theTe vas a ocupar de esta consulta
toast, because the backend is updated but the view isn't. The button stays desynced untill the page is refreshed.A possible solution is not allowing any actions if 45 minutes have passed since the page was loaded (this would have to be done on JS). In any case it's probably a good idea since after such amount of time there might be new comments, the discussion could have changed status, someone else might be in charge now anyway, etc.
This is not urgent and probably won't happen very often, but I thought I'd leave it documented.
The text was updated successfully, but these errors were encountered: