Stop logging project locked messages in timeline? #1970
Labels
app: landingzones
Issue in the landingzones app
app: taskflowbackend
Issue in the taskflowbackend app
feature
Requested feature or enhancement
tbd
Comments wanted, spec/schedule/prioritization to be decided, etc.
I've noticed that it's very easy for users to clog up the project and admin timelines by spamming landing zone operation requests on a locked project.
While it's still important for the user to receive this message and e.g. the zone status message to be updated, this is somewhat worthless from the timeline perspective and only serves to fill up the logs with redundant information.
I'll have to think this in detail to ensure there is not a valid reason to include these messages in timeline.
Other related errors such as a unreachable locking service due to a Redis error should still be displayed, of course. This applies to where the project is locked by another operation and the current operation is rightfully denied.
The text was updated successfully, but these errors were encountered: