A Schedule instance is only deleted after the task is queued if its scheduled type is Schedule.ONCE and repeats == -1, which is non intuitive to the user.
the online documentation says that the task will be queued indefinitely if repeats == -1 (I assume that's "always" means), but that's not true for tasks with schedule type Schedule.ONCE. Why do we even need a Schedule.ONCE schedule type if the user can create a Schedule instance with repeats=1 ? Having both Schedule.ONCE as a schedule type and the repeats argument set to a value different that 1 in the same task doesn't make sense.
Schedule instances should be consistently deleted when the task is queued, regardless of schedule type. If the library wants to parameterize the Schedule deletion, it could be done consistently with an argument like delete_after_queued.
A Schedule instance is only deleted after the task is queued if its scheduled type is Schedule.ONCE and repeats == -1, which is non intuitive to the user.