Schedule end date changes after saving schedule

[Diederik_vanderharst]

Hi all, I've been running into this from time to time and I wonder if anyone recognizes this or knows a fix for it.

I regularly schedule flows, or edit schedules. Sometimes I trial run a flow for couple of days, let's say 3 days. So I set a end date for today plus 3 days. Sometimes that works fine, but since I've been testing a lot lately I've noticed the end date often changes to a week later or even several months later, to even a random date in 2027 after saving the schedule. As the end date is not shown in the first overview of a schedule, I now return to edit the schedule to double check the end date. I really do not like this unpredictable behaviour.

Please let me know your experiences and potential fixes.

Thanks!

[MinhLO]

Hey @Diederik_vanderharst ,

Recent Upgrade to 2025.1 Issues - Alteryx Community - in this list you will notice there are a lot of issues regarding schedules.

Quoting Alteryx:
" As a result, previously scheduled workflows without a defined ClientType are not recognized properly in the updated Designer version, leading to the behavior you're seeing".

Hence I would definitely think this is a bug and they will fix the overall schedules in the next minor.

[stacihoover109]

---

@Diederik_vanderharst EZPassCT login wrote:

Hi all, I've been running into this from time to time and I wonder if anyone recognizes this or knows a fix for it.

I regularly schedule flows, or edit schedules. Sometimes I trial run a flow for couple of days, let's say 3 days. So I set a end date for today plus 3 days. Sometimes that works fine, but since I've been testing a lot lately I've noticed the end date often changes to a week later or even several months later, to even a random date in 2027 after saving the schedule. As the end date is not shown in the first overview of a schedule, I now return to edit the schedule to double check the end date. I really do not like this unpredictable behaviour.

Please let me know your experiences and potential fixes.

Thanks!

---

Hello,
It sounds like a known scheduling bug where the end date doesn’t persist correctly after saving. The best workaround is to always re‑open and confirm the schedule after saving, or set the end date using advanced options/PowerShell to ensure it sticks. If it keeps happening, raise a support ticket with Microsoft as it’s not expected behavior.

Best Regards,
Staci Hoover