@lioz Thanks for reaching out and apology for the inconvenience due to this issue.
I tried to reproduce the issue at my end for both standard and consumption logic app but couldn't reproduce the issue for consumption logic app or standard stateflow workflows.
Please confirm if you are observing this behavior in the standard stateless workflows as this is expected behavior as documented here.
The Recurrence trigger isn't associated with any specific service, so you can use the trigger with almost any workflow, such as Consumption logic app workflows and Standard logic app stateful workflows. This trigger is currently unavailable for Standard logic app stateless workflows.
Let me know if you have any queries or concerns.
Please 'Accept Answer' if it helped so that it can help others in the community looking for help on similar topics.