Schedled jobs still execute in a canceled batch after the batch expired

bug?
1

Hi,

We’ve experiened a weired situation when using batch.

The scenerio is:

  1. We start a batch with scheduled jobs, some of the the schedule time of the jobs are later than batch expiration. (For example, batch expiration is 1 min, one shceduled job will be executed after 2 min)
  2. After the batch started, cancel it before it expired.
  3. The scheduled jobs with execution time before batch expiration will be deleted, but the jobs with execution time after the batch expiration will still be executed.

Is it by design?

May I know if there will be any impact if we set the batch expiration to more than 3 months?

Thank you.