My status will not update from away to available unless I activate the teams window.
My teams status will update to away automatically, but I've noticed that after returning to the computer, the status remains "away" unless the teams window becomes the active window. Once I activate the teams window again, the status will reset automatically after a few seconds. However, this is not intuitive, if I have teams running in the background, it will show me as away even if I've been back and active on my computer for hours, and I won't even be aware.
PRETTY WIDESPREAD ISSUE:
2. (the thread where Alex requests logs; also the largest vote count and the only *open* thread with a MS response) https://microsoftteams.uservoice.com/forums/555103-public/suggestions/19544905-incorrect-status-in-teams
6. (thread closed but comments said still occurring) https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18629083-don-t-switch-to-away-just-because-i-m-using-a-d
14. THIS THREAD
Menaka Purushothaman commented
I am facing the same issue. It beats the purpose of having the setting the status with Duration.
Stu H. commented
I (and the people I work with) are suffering from this same bug ever since the company I work for changed our default communications app from SfB to Teams a few weeks ago.
As Scott indicates, when the computer goes into the "Away" status, after being inactive for more than 5 minutes, it doesn't return to "Available" unless I select the Teams window. As we are still working from home during the pandemic, this has been a real issue.
There are a number of similar threads to this one with the same/similar issue, and this has been reported for over 4 months now. When are you going to acknowledge this bug and fix it?
Still happening to several of our users too.
I have the same issue. Essentially, unless I am actively using the Teams application it changes my status to 'away', despite the fact I am actively using my keyboard and mouse on other applications while Teams is in the background.
This was reported previously and a representative of Microsoft Teams claimed the issue had been fixed by a back-end change in March. I am here to confirm that this issue is not fixed and is still affecting users including myself.