ContinueAsNew Loses Cron Schedule: Why?


I have noticed that a continue-as-new will result in the cron schedule NOT propagating to the new workflow run. This seems to be a feature according to this post Temporal Cron Questions - #9 by tihomir

Why is that the case? It doesn’t really make sense to me as desired behaviour. Is there an easy way to work around this? I’m trying to use a continue-as-new to avoid a very large event history.



We are about to release the Schedules feature that fixes most cron workflow issues.

As a workaround to your problem, I would use a child workflow that calls continue-as-new.

Ah, okay. Thanks!