AR
Ali Ryder
🧑💼 Staff
over 1 year ago
In Progress
Stored procedure sp_CheckClientState not being initiated
Every night, the stored procedure sp_checkClientState is supposed to run, which is supposed to check each client's date of last activity and update their activity/inactivity status accordingly. It appears that this procedure is not always being called when it is supposed to, which is resulting in a number of issues related to activity/inactivity.
🚦Activity Status
4.0.61.1
4.0.60.5
4.0.60.4
4.0.60.3
🚨Major
🐛Bug
Copyright © 2026 ACRE Consulting
___MESSAGE___
___MESSAGE___
Seems to still be an issue in 4.0.61.1.3. I took a copy of production and upgraded it to 4.0.61.1.3 on Monday, on Tuesday morning I saw many clients that were still active that should not have been. I manually ran the sp_CheckClientState stored procedure and they became inactive.
@Christie Scott I'm actually not surprised. The changelog specifically states it updated sp_UpdateClientChronicityStatus and sp_UpdateClientHousingStatus, but sp_CheckClientState was not explicitly mentioned in the release notes.
Idea Clients are going over the inactivity threshold but not becoming inactive (60.3) was merged into this idea.
Idea Being booked at a shelter no longer refreshes activity daily - 60.4 was merged into this idea.
You can temporarily fix this by manually executing the stored procedure sp_CheckClientState in your HIFIS database. If you don't know what that means, this instruction is not for you. Talk to your database administrator. However, this only corrects your current data and doesn't prevent future problems.
@Ali Ryder I have a SQL job scheduled to run this shortly after midnight nightly in 60.3 to work around the issue. Hoping that I can disable it after upgrading, but we will see.
@Christie Scott Oh yeah that should work
See also:
Clients are going over the inactivity threshold but not becoming inactive (60.3)
RecentActivityDateTime is null
Stored procedure sp_CheckClientState not being initiated