starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #1775] Pending Actions not clearing after scheduling reboot #3046

New issue

Open

opened 2026-03-14 06:21:32 +03:00 by kerem · 6 comments

kerem commented

2026-03-14 06:21:32 +03:00

Owner

Originally created by @SIDrumm on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1775

Server Info (please complete the following information):

OS: Ubuntu 22.04.4 LTS
Browser: Chrome Version 121.0.6167.189
RMM Version (as shown in top left of web UI): v0.17.5

Installation Method:

Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): Agent v2.6.2
Agent OS: Windows Server 2022 Datacenter, 64 bit v21H2 (build 20348.2322)

Describe the bug
When you schedule a reboot via the built-in reboot functionality, the pending action doesn't clear following the completion of the reboot. As of writing, it's been at least four days since the actions were completed and they're still not cleared.

To Reproduce
Steps to reproduce the behavior:

Go to 'Agent'
Click on 'Reboot'
Scroll down to 'Later'
Set reboot for that night, to find pending action does not clear the following morning.

Expected behavior
For the pending actions to clear shortly after the action is complete.

Additional context
This is happening across all versions of Windows server, from the one listed, all the way down to Windows Server 2012 R2. We also noticed that a handful didn't reboot despite the action completing and the scheduled task being found in Windows. However, we're not certain this is the fault of Tactical RMM.

I've found that pruning DB tables and clearing cache can sometimes help, along with putting server agents in maintenance mode and regularly trying to clear the cache and reloading the RMM. Doing this managed to clear the pending actions of two servers, however it's not known exactly what cleared them and the same steps haven't worked on the others.

Originally created by @SIDrumm on GitHub (Feb 27, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1775 **Server Info (please complete the following information):** - OS: Ubuntu 22.04.4 LTS - Browser: Chrome Version 121.0.6167.189 - RMM Version (as shown in top left of web UI): v0.17.5 **Installation Method:** - [X] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): Agent v2.6.2 - Agent OS: Windows Server 2022 Datacenter, 64 bit v21H2 (build 20348.2322) **Describe the bug** When you schedule a reboot via the built-in reboot functionality, the pending action doesn't clear following the completion of the reboot. As of writing, it's been at least four days since the actions were completed and they're still not cleared. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Agent' 2. Click on 'Reboot' 3. Scroll down to 'Later' 4. Set reboot for that night, to find pending action does not clear the following morning. **Expected behavior** For the pending actions to clear shortly after the action is complete. **Additional context** This is happening across all versions of Windows server, from the one listed, all the way down to Windows Server 2012 R2. We also noticed that a handful didn't reboot despite the action completing and the scheduled task being found in Windows. However, we're not certain this is the fault of Tactical RMM. I've found that pruning DB tables and clearing cache can sometimes help, along with putting server agents in maintenance mode and regularly trying to clear the cache and reloading the RMM. Doing this managed to clear the pending actions of two servers, however it's not known exactly what cleared them and the same steps haven't worked on the others.

kerem commented

2026-03-14 06:21:38 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Apr 9, 2024):

i have the same behavoir.

@P6g9YHK6 commented on GitHub (Apr 9, 2024): i have the same behavoir.

kerem commented

2026-03-14 06:21:44 +03:00

Author

Owner

@silversword411 commented on GitHub (Apr 11, 2024):

Check pending actions 60mins after it completes.

Still showing as pending?

There was a pending actions bug...I think it was fixed, but the task that's moving from pending to finished is more of a turtle update than a hare update.

@silversword411 commented on GitHub (Apr 11, 2024): Check pending actions 60mins after it completes. Still showing as pending? There was a pending actions bug...I think it was fixed, but the task that's moving from pending to finished is more of a turtle update than a hare update.

kerem commented

2026-03-14 06:21:49 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Apr 13, 2024):

Yep its more a question of days/weeks than minutes

@P6g9YHK6 commented on GitHub (Apr 13, 2024): Yep its more a question of days/weeks than minutes

kerem commented

2026-03-14 06:21:54 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Apr 22, 2024):

now months :/

@P6g9YHK6 commented on GitHub (Apr 22, 2024): now months :/

kerem commented

2026-03-14 06:21:59 +03:00

Author

Owner

@pierreparre commented on GitHub (Apr 2, 2025):

Bump. I do have the same problem,
Docker install, latest version (1.0.0).
Doesn't clear for a few hours

@pierreparre commented on GitHub (Apr 2, 2025): Bump. I do have the same problem, Docker install, latest version (1.0.0). Doesn't clear for a few hours

kerem commented

2026-03-14 06:22:04 +03:00

Author

Owner

@insanity67 commented on GitHub (Jun 10, 2025):

Same problem here, pending tasks icon never disappears, even after several days. Manually fiddling with clearing cache, running background tasks etc helps, but only for one host at a time.

@insanity67 commented on GitHub (Jun 10, 2025): Same problem here, pending tasks icon never disappears, even after several days. Manually fiddling with clearing cache, running background tasks etc helps, but only for one host at a time.