State Machine Workflow - Event Driven - Need a State Transfer?

Inside a state machine, if an event is handled inside an event driven event, is a state transition (i.e. SetStateActivity) required?

My goal is to allow the same logic within a certain event-driven activity to repeat itself (by signaling multiple times) until a certain condition is met, at what time the state should transition and the process will repeat for the next states.

Currently, in the case where no state transition occurs, it looks like the event-triggered activity finishes and then the entire workflow exits (i.e. all activities are closed), but when viewing the tracking data, the instance workflow indicates that it is was interrupted.