Log Shows Modified By User When Isn't

Question

Hello,

I am having an issue where Adaxes is logging that I modified the scheduled task and a Custom command when I didn't.

This can be replicated by opening any scheduled task or custom command and making a change to it. This however seems to happen only if you change something about an existing item in the list such as modifying the text in a script, changing an action to block instead of allow, or even opening a script in a custom command but hitting cancel on everything and not saving anything by hitting cancel here:

However, it still logs that I "Modified" it when I did not save anything:

This of course causes issues and incorrect actions and if a logs says I modified something and I didn't, it makes it harder for admins to find out when it was truly modified last and by who.

This does not seem to affect report or property pattern changes that do not get saved, as those do not show in the log as being modified. Such as changing a report column preferences or editing a default property pattern value but not hitting save on the orange bar pictured above.

I am using the latest version of Adaxes (Update 3), and I know this issue exists in the previous Update 2 as well.

Answer 1

Hello,

Thank you for pointing out the issue. We forwarded the details to the corresponding department.

Comments

Is this a known issue? Can your team replicate the issue? Wondering what the timeline is for the next update for Adaxes.

---

Hello,

Yes, we are able to reproduce the behavior. It will be fixed in one of the future releases. Unfortunately, there is no estimate for the release of the fix.

---

Adaxes, you have had 3 updates since this release with the issue and the issue is still not fixed? We updated to the latest 2025 and the logs still improply shows that me as an admin updated a command when I never saved anything. All I did was open the script. No changes were done. This is very bad for your logs to lie and put our admins in a position where we have to ask if they really updated or not. Making it impossible to know who actually made a change.

Why has this critical logging issue not been fixed? It's only when you have a command with a powershell script and you open the script in the editor to view it. Viewing only is not an "Update" action.

---

Hello,

We totally understand your frustration, but the issue cannot be fixed just locally. It is part of a very big mechanism that is being reworked. We apologize for the inconvenience, but the fix will also not be included into the next major release. Unfortunately, there is currently no ETA for it.