Hey, thanks for the report. I see the screenshots. The cron 0 8 * * 1-5 should only run on weekdays, but Run History shows weekend runs too.
This is a known issue. When updating a cron schedule, the old entries in the scheduler weren’t fully replaced, so they kept piling up. The server-side fix is already deployed, but for existing automations you need to force an update:
Open the automation settings
Make any small change (for example, change the time and then change it back)
Save
This should clear the stale schedule entries. If it still doesn’t help, try deleting the automation and creating it again with the same cron.