Closed matthewtomo closed 1 week ago
Hi @matthewtomo,
As per screenshot, this timeout issue has been known for quite some time, but unfortunately, it cannot be resolved through the SIM UI. The resolution of this matter must be addressed by Forio.
@tejaspesquare Do you know if this is related to our use of the V3 Forio API?
@matthewtomo
Will you please add a current clarification for our communication with learners using the simulation in the field?
It sounds like @tejaspesquare is saying that current state is such that if any single user runs the simulation at the same time from any world Sim UI PROD fails. Is that correct?
FYI: @jamesmrollins
@lzim, It looks like this is the case. I will be emailing David from Forio shortly to set up a meeting and uncover the cause of this issue.
@dlounsbu @dlkibbe This was the issue we encountered on the Monday support, systems_sme, & sim_ui workflows sync meeting. The Sim UI should still work as expected when only one person is using it. Avoid starting multiple simulation sessions at the same time.
fyi: @jamesmrollins @tejaspesquare @lijenn @ljmoody
Alert message included in the Sim UI:
The Sim UI is currently encountering an issue where simulation sessions will fail to run if more than one user attempts to start a session at the same time.
If after starting a session your page enters a loading screen for more than 30 seconds, the best course of action is to refresh the page and try again in a few minutes.
We are actively working to resolve this issue.
Hi Matthew,
@tejaspesquare Do you know if this is related to our use of the V3 Forio API?
This is unrelated to V2 or V3 API and not sure if this is linked with multiple user sessions. We have observed this error even when only a single user session is active.
@matthewtomo, when more information is known about this via David at Forio, please let me know if a clarification message is needed in the MTL 3.7 Consult Manual and what the limits are for users, etc. so the wording is specific and clear. Thank you!
Discussed Dev Standup wk_1 2024_10 @matthewtomo @tejaspesquare
@matthewtomo - Keep in really close communication with #systems_sme_workflow about the impact of this on their PREP.
FYI: @dlounsbu @dlkibbe
Discussed Monday Dev Standup wk_2 2024_10 @matthewtomo @tejaspesquare
@matthewtomo
Please estimate scope and timeline for impacted users and add to agenda for #9am_workflow leads
#consult_workflow MTL 3.7 Blue Consult PREP #systems_sme and workflows: #consult_workflow
FYI: @dlounsbu @dlkibbe Thanks!
wk2 2024_10 - #sim_ui_workflow @lzim @matthewtomo @ljmoody
_1. Why/how_ -> rationale/intent -> why you're going about it the way you are.
2. ANDON -> impact on quality of relationship with partners, user experience.
3.Meetings: Slow velocity (story points/week) Decision or Discussion to unstuck.
4. Possible requirements and scope in story points and when delivered:
#workflow_users - Laura, Matthew, Lindsey #user_workflows - #consult_workflow #support_workflow
5. Rule out approaches by users, timeline & scope
[ ] 1.#sim_ui - Next Steps: Expand_ timeout threshold to 30 seconds -> Matthew is testing wk2 2024_10 Forio support thru Feb 2025 -> meets the VHA size scale of client
[ ] 2. #sim_ui - Message in the DDD in red font 2 pts -> Pop-up: "We detect a slow network. Please refresh your browser and click Go again."
[ ] 3. #systems_sme_workflow - @dlkibbe @dlounsbu need training in how to handle the delay live with sites add to wk4 2024_10 #9am_workflow leads.
Discussed Friday Dev Standup wk2 2024_10 @matthewtomo @tejaspesquare
Discussed Friday Dev Standup wk2 2024_10 @matthewtomo @tejaspesquare
- @matthewtomo @tejaspesquare will await response from David at Forio in order to ensure that our timeout limit increase is being handled correctly
Thanks @matthewtomo - Let's keep a close eye on this for the consults next week!
Discussed Friday Dev Standup wk3 2024_10 @matthewtomo @tejaspesquare
fyi: @lzim
Thanks for the update on this @matthewtomo
From #9am_workflow leads today: @lzim @matthewtomo @ljmoody
Discussed #support_workflow wk4 2024_10 @matthewtomo @lzim
fyi: @ljmoody @dlkibbe @dlounsbu
Discovered 7/29/2024 by Debbie, Laura, Jenn and Matthew in PROD instance.
Debbie informed us that this is a major issue, since facilitators are often having clinicians run simulations on their own computers at the same time.