You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When syncing templates back to devices, no feedback is shown on screen once the "Continue" button is pressed. This means, you have no idea whether there is anything occurring and/or it is errored/locked up.
To Reproduce
Steps to reproduce the behavior:
Modify a template with a large number of items based upon it.
Sync changes and after clicking continue, see nothing back.
Expected behavior
Long running processes such as this should use a background process to execute with a status display returned that the front end can display whilst it is in progress.
Ideally, long term, all actions should operate this way to provide consistency.
Screenshots
Additional context
Any request made to the web should take no more than 5-10 seconds to complete. This prevents issues were users believe that they have either broken something or it's not running at all.
The text was updated successfully, but these errors were encountered:
Yea, this whole thing should be backgrounded if it's going to take that long. I really don't know why it takes so long actually. I'll do a quick check. I suspect is re-running all queries, which should not be happening.
Okay, I've made an update that should make things very fast now, especially if there are no changes. As a feature request, we should allow this process to be backgrounded if you have thousands of devices and your are adding a few large data queries.
Describe the bug
When syncing templates back to devices, no feedback is shown on screen once the "Continue" button is pressed. This means, you have no idea whether there is anything occurring and/or it is errored/locked up.
To Reproduce
Steps to reproduce the behavior:
Modify a template with a large number of items based upon it.
Sync changes and after clicking continue, see nothing back.
Expected behavior
Long running processes such as this should use a background process to execute with a status display returned that the front end can display whilst it is in progress.
Ideally, long term, all actions should operate this way to provide consistency.
Screenshots
Additional context
Any request made to the web should take no more than 5-10 seconds to complete. This prevents issues were users believe that they have either broken something or it's not running at all.
The text was updated successfully, but these errors were encountered: