The story:save event should be triggered every time the article is saved. Unfortunately, this event is currently only available for articles that have not yet been published. However, if this is important for the intended use, it is possible to check beforehand whether this article has already been published. An event should therefore always be triggered and each system can check accordingly whether this event is relevant or not.
I'd like to extend my original proposal with an additional important point:
In addition to triggering the story:save event for both published and unpublished articles, I believe it's crucial that this event should also be fired during auto-save operations.
Currently, there are two limitations preventing us from effectively utilizing the story:save event:
The event is only triggered for unpublished articles (as mentioned in my original request).
The event is not triggered during auto-save operations.
These two limitations combined are significantly hindering our ability to use the story:save event effectively. By addressing both issues, we would greatly enhance the functionality and usefulness of this event.
I appreciate your consideration of this extended feature request. Implementing both aspects - triggering the event for all articles regardless of publication status and during auto-saves - would provide a much more comprehensive and reliable way to track article modifications.