Currently, this action only works for a single event. If a workflow can be triggered by multiple different events, such as schedule + workflow_dispatch, then this breaks the continuation between those dispatches, for example, action triggered by schedule will not detect last successful action from the same workflow, triggered by workflow_dispatch

Could we add an option to ignore this variable or ability so specify more than one valid value?

This is a reopen of the #142 / #155. Suggested workaround does not solve the issue, because even setting a dynamic last-successful-event still only listens for a single event.