-
Notifications
You must be signed in to change notification settings - Fork 7
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
Error messages incorrectly displaying #40
Comments
Are there particular circumstances that bring this about? Steps to repro would be helpful in this case. |
I've also encountered this. No idea how to reproduce it. This is where good
|
I think has a higher chance of occurring when submitting PDF files. It might even only happen when submitting PDF files. |
I think the first step is to implement some logging so that whenever Remember how we poll the cloudprint history to check if something actually There's no way of knowing untill we have better logging. So the first step
|
I'm pretty sure I figured it out. It is because in |
Yah, that's probably it.
|
Another problem with |
Do you think processing time increases linearly with file size? If so, it
|
What's wrong with not deleting cloud print history? Does it break if
|
Yeah I'd guess processing time increases linearly with file size. |
Never mind about the cloud print history. Being slower would be beneficial in this case. Sort of. |
Sometimes when submitting a document to print, an error message will appear saying "Sorry! Something went wrong while we were submitting your print job. Please try again", but when the user refreshes the page, their queue shows that the document was successfully submitted to uniFLOW.
The text was updated successfully, but these errors were encountered: