Settings and activity
693 results found
-
2 votesJeremy Shieh supported this idea ·
-
5 votesJeremy Shieh supported this idea ·
-
2 votesJeremy Shieh supported this idea ·
-
14 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
5 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
2 votesJeremy Shieh supported this idea ·
-
4 votesJeremy Shieh supported this idea ·
-
2 votesJeremy Shieh supported this idea ·
-
4 votesJeremy Shieh supported this idea ·
-
8 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
5 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
37 votesJeremy Shieh supported this idea ·
-
3 votesJeremy Shieh supported this idea ·
-
4 votesJeremy Shieh supported this idea ·
An error occurred while saving the comment -
11 votesJeremy Shieh supported this idea ·
I have run into this many times as well but didn’t have the explicit data to back up my hypothesis that if an appointment was moved AFTER the confirmation window for sending a confirmation message has passed, then there will be no further confirmation message. Or if the appointment has been moved but was previously confirmed, it retains its confirmed status and also does not send a message out to confirm.
After confirming these scenarios by intentionally replicating them, I now agree with this idea in that this is not an edge case and perhaps retained inconsistencies with what we feel the software should be doing and what it is performing based on “perfect” operations being in conflict.