@JoshVee On which version of Coder are you seeing this behaviour?

Put in the next sprint:

1. to reproduce
2. to understand whether this was a regression
3. fix this
4. identify whether there is room for larger improvement in Coder's activity detection

@bpmct is it possible that this was fixed by #11603?

I believe this should have been fixed by d583aca, which was included in 2.7.0 and later releases. Can anyone confirm if they are still seeing this behaviour?

Autostop is determined by the deadline of the workspace build so if we're just updating last_used_at then probably not?

Given that you can override the agent stats reporting interval, I wonder if setting this to a sufficiently high value could cause this behaviour?

Given that you can override the agent stats reporting interval, I wonder if setting this to a sufficiently high value could cause this behaviour?

The apps do not report metrics via the agent stats. So the agent stats reporting interval does not change this behavior.

My draft PR does fix this, but we should implement a batch sql query to handle this. The looping feels like it could be a performance hit.

EDIT: @johnstcn mentioned the connection count on the agent. See

#12916 (comment)

I think this is resolved already.

I am closing out this issue for now as "cannot reproduce". Please do not hesitate to re-open it if you have more information!

In any case, we ensure this issue does not resurface when revamping activity detection (see: #12965)