mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #2063] Web Portal - 1st attempt to select returns ALL agents globally #3228
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#3228
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zoltan151 on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2063
After logging into the Web Portal in a new session, the 1st attempt to select a client group always returns ALL agents, globally. You then have to click on a different client group, wait for it to finish loading, and click the client group you tried navigating to in the first place. If you don't wait for it to finish loading the 2nd/temporary client group, and try clicking on the 1st client group again too quickly, then it oftentimes has the same issue occur and show all global agents in the dashboard.
Browser: Google Chrome
Server OS: Ubuntu LTS 22.04
Client OS (accessing from): Windows 11
Running TRMM v0.19.4
@P6g9YHK6 commented on GitHub (Nov 7, 2024):
experiencing the same bug
@mrdeanwalker89 commented on GitHub (Nov 22, 2024):
I thought it was just me going mad. but yeah same things happens to us and drives me nuts!
@silversword411 commented on GitHub (Nov 23, 2024):
It's an interaction with the time it takes to load the agent list payload and the caching stuff.
Be patient on that first click, wait for the full agent list to load before clicking a client/site to avoid. Use your browser dev console to see the time for your agent payload list (network > look for the /agents/ item to see how long your server takes to get the agent list)
This is a workaround till backend queries are optimized.
@eduardoglazar commented on GitHub (Dec 17, 2024):
This would be solved with a simple home screen results pager.
@zoltan151 commented on GitHub (Feb 4, 2025):
I think the simplest and easiest solution would just be to have it not automatically load "all clients" by default. Why not just have the home screen not load any agents into the list at all, until a selection is made? Currently, the default selection after log-in is the "All Clients" link.... Maybe don't load all clients unless the user actually clicks on "All Clients"? This would dramatically reduce the loading time as well as query-induced load on the server resources, especially when there are multiple users and many agents.
@silversword411 @wh1te909 Thoughts?
@richardlg-pro commented on GitHub (Apr 29, 2025):
Any news about this?
We have a total of 1916 agents at the moment, with more to come, and the tool loads all the agents on the first access, hence the very slow first loading (15 seconds) and the sluggish behavior.
Indeed, why not add a page results system?
@zoltan151 commented on GitHub (Sep 10, 2025):
Bump
@wh1te909 commented on GitHub (Dec 16, 2025):
pagination is in progress as part of a big frontend rework. in the meantime, I've just added some more db optimizations and caching which improves the loading times by around 4x from my testing. for example an instance with 1700 endpoints used to take avg 12 seconds to load, now takes 3 seconds. you should see a nice speedup in the next release