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

Simulator Issues #3112

Open
KrishnaDwibhashi2 opened this issue Oct 8, 2024 · 4 comments
Open

Simulator Issues #3112

KrishnaDwibhashi2 opened this issue Oct 8, 2024 · 4 comments
Assignees

Comments

@KrishnaDwibhashi2
Copy link

KrishnaDwibhashi2 commented Oct 8, 2024

Simulator on Glific UI always often gives different issues (which are non-replicable). There were fixes made earlier (link), but the issues persists.

Here are some of the commonly observed issues-

  • Flow not starting (old flow still going on/ new flow not starting). It this case often keyword is sent, but there is no response.
    In these cases, if we cancel & reopen simulator, then the flow gets continued
    image

  • Input is taken incorrectly- it can be either keyword/ input given

@radhikaT4D
Copy link

@KrishnaDwibhashi2 a few questions:

  1. which browser were you using. Does it happen on any browser?
  2. Also if possible try to capture a clip when this issue happens, and attach here, with a timestamp, for devs to review.

@kurund
Copy link
Contributor

kurund commented Oct 9, 2024

@KrishnaDwibhashi2

Also wondering if this happens only to specific flows such as when webhooks are part of the flow?

@KrishnaDwibhashi2
Copy link
Author

@kurund No, it happens in normal flows too where there are no webhooks, but just basic features like interactive messages, send message, wait for response, update contact etc

@radhikaT4D I use chrome browser- hasn't tested on other browsers, but many ngos reported it multiple times (so I am assuming its not browser specific)
I will capture it next time and share

@kurund
Copy link
Contributor

kurund commented Nov 7, 2024

@KrishnaDwibhashi2

As mentioned during one of our calls, I do have some sort of idea for this weird behaviour. I need to investigate a bit more to confirm and then work on the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants