If your account is locked or your password expired, your Scheduled Tasks will fail to execute.
When you create a Triggered Task and change the Run Policy to Scheduled, the Triggered Task URLs are not disabled. Therefore, the underlying pipeline is still executable through the Triggered Task URLs, even though the Task is now a Scheduled Task.
Workaround: create a new Scheduled Task asset referencing the target pipeline and disable or delete the Triggered Task.