You can check the trigger on the output of the trigger action, just open the run instance from your flow's main page. If it is not helping, you can modify your flow to add a 'Terminate' action right after the trigger action, so it will not take up resources despite the continuously starting state.