-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue in bed occupied status #8436
Comments
Hey @khavinshankar as I have gone through BedSelect component in BedSelect.tsx. I noticed it is return empty array for the data we are fetching from backend and I am logging the raw data fetched not any filtered condition applied so probably it is a backend issue only . Here are screenshots : cc: @rithviknishad |
Steps to reproduce and the expected behaviour would really help in understanding the issue better. Kindly mention if possible @khavinshankar @rithviknishad |
@Sulochan-khadka @AdityaJ2305 this was due to a race condition that was reproducible in an older version. However likely that the duplicate ConsultationBed records that were created on those days were not cleared. @khavinshankar we can close this issue right? cc: @sainak |
Closing this issue as completed. |
In location Management it has been showing that all beds are occupied but actually, they are Not Occupied. Only a few of them are occupied.
Occupied Beds:
Location:
Unable to select bed:
Reported by: Nagnath
cc: @nihal467
The text was updated successfully, but these errors were encountered: