Misleading Audit Log Entry After Instance Rollback
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
### Current Behavior
See also: https://github.com/flowforge/flowforge/issues/2554
> In the audit log, it says I logged in to FlowForge after the rollback is finished. This seems like an odd message since I never logged out. There is also a message that 'Node-RED has stopped - something has gone wrong' which is not the case since it was a rollback.
### Expected Behavior
The audit log should display only one entry, specifically "Instance Rolled Back," without any other entries.
### Steps To Reproduce
1. Initiate the rollback for the selected instance.
2. Check the audit log and observe the incorrect entries.
### Environment
- FlowForge version: FF-Cloud - 1.9
- Browser: Chrome
### Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Contributor guide
Research direction
Start by reproducing the selected instance rollback and reviewing the resulting audit log entries, including the login and Node-RED stopped messages. Trace the rollback flow and its audit events, then verify that the audit log contains only “Instance Rolled Back” and no misleading status entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100