Skip to content
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

Assign Bed throws error "Cannot create conflicting entry" even though no bed was allocated previously #6748

Closed
rithviknishad opened this issue Nov 29, 2023 · 9 comments
Labels
Backend bug Something isn't working

Comments

@rithviknishad
Copy link
Member

rithviknishad commented Nov 29, 2023

Describe the bug
Assign Bed throws an error "Cannot create conflicting entry" even though no bed was allocated previously

To Reproduce
Steps to reproduce the behavior:

  1. Attempt to assign bed for this consultation

Expected behavior
If the bed is already occupied, the option for selecting such beds should be disabled by either showing "Occupied" badge or the bed should be hidden.

Otherwise, if there are no conflicting entries, it should allow to assign the bed.

Screenshots
image

@rithviknishad rithviknishad added the bug Something isn't working label Nov 29, 2023
@github-project-automation github-project-automation bot moved this to Triage in Care Nov 29, 2023
@rithviknishad
Copy link
Member Author

Bed is vacant too btw

image

@sriharsh05
Copy link
Contributor

I want to work on this issue. Please assign it to me.

@rithviknishad rithviknishad moved this from Triage to Up Next in Care Nov 29, 2023
@sriharsh05
Copy link
Contributor

@rithviknishad
I have a doubt regarding this issue. When I try to assign or switch a patient to another bed, the feature works perfectly fine. However, the error only occurs with the bed you provided (eafefo). I even attempted to create new patients and assign them to that bed (eafofo), but it still throws the same error. There doesn't seem to be any issue with the new beds created. Is it possible that the problem lies only with that specific bed, or am I missing something?

@sriharsh05
Copy link
Contributor

The bed eafefo was created on "2022-07-15T12:44:16.229074+05:30". Can the problem be related to the creation date of that bed?

@rithviknishad
Copy link
Member Author

How would the creation date of that bed be a problem? It could be a problem with that specific bed, but what exactly is the problem? If it's vacant, then it should be assignable with current time right?

Copy link

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.

@github-actions github-actions bot added the stale label Dec 16, 2023
@sriharsh05 sriharsh05 removed their assignment Dec 28, 2023
@github-actions github-actions bot removed the stale label Dec 29, 2023
@Pranshu1902
Copy link
Contributor

@rithviknishad I am not able to recreate the issue, I can assign that exact bed eafefo to patients with or without bed history
Example Patient

@sriharsh05
Copy link
Contributor

@Pranshu1902
The error message is thrown when you change beds with in same minute.
To reproduce:
Switch a patient within 2 fixed beds alternatively.

@Pranshu1902
Copy link
Contributor

@Pranshu1902 The error message is thrown when you change beds with in same minute. To reproduce: Switch a patient within 2 fixed beds alternatively.

yeah, I guess that is intentional to block switching withing the same minute

@rithviknishad rithviknishad closed this as not planned Won't fix, can't repro, duplicate, stale Dec 30, 2023
@github-project-automation github-project-automation bot moved this from Up Next to Done in Care Dec 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

4 participants