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

Stopping records sometimes alert "This action has not been executed" but it's actually done #6

Open
jdulb opened this issue Dec 18, 2015 · 1 comment

Comments

@jdulb
Copy link
Collaborator

jdulb commented Dec 18, 2015

The action is still executed.
This happens when the service spend too much time responding. Timeout increase has been done as a temporary fix, but no web service should ever take so much time (> 10s) to respond.

@jdulb jdulb changed the title Stopping records sometimes alert "This action has not been executed" for no identified reason Stopping records sometimes alert "This action has not been executed" but it's actually done Aug 29, 2016
@jdulb
Copy link
Collaborator Author

jdulb commented Aug 29, 2016

This also cause the UI to be out of sync with the real current recorder state.

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

1 participant