@lmajano I'm running into an issue with ColdBox 7 scheduled tasks. It seems that when a task fails or errors out, the task never runs again. I have occasional API call issues or SQL deadlock issues. They are usually one-offs and don't justify not running again. How do I prevent the task from stopping completely?

Are you catching the error or letting it bubble up?

LogBox sends me an email on them, but they are pretty irrelevant. Maybe one or two a day.

That wasn't what I asked

No, I am not catching the error. If it fails, it gets caught up the next time it runs.

Right or wrong, catching the error and not rethrowing it will likely stop your task from dying

@bdw429s I'll look into that for the API errors. On the other hand, the occasional SQL deadlocked transaction could be any single query. That's more of a time-sink to handle all of those. Thanks!

@Cavan Vannice To be clear, I'm not suggesting you wrap a bunch of individual bits of code inside your tasks with try/catch. Just do one at the top level to prevent any exceptions from bubbling up to the Java thread

task( "my-task" )
    .call( () => {
       try {
         yourService.yourTaskLogic();
       } catch( any e ) {
          // Error logging here so you still know about the errors.
       }
    } )
    .everyHour();

Ah, that makes more sense. I'll give that a try!

All errors on scheduled tasks are trapped

@lmajano Ok, thanks.