Task is picked but not executed

[viniciusccarvalho]

Hi folks, I just started looking into this project. I have used quartz a few times a long time ago, and I'm no stranger to Spring Boot.

However when I try to configure the scheduler to run an adhoc task (for production use we will actually have recurring tasks, this is just a way to run a task adhoc via a controller to test things).

I see on the table that the task is picked up, but it is never executed.

here's my enqueue service:

 private static final Logger logger = LoggerFactory.getLogger(EnqueueService.class);
    private final Map<String, JobRunner> jobRunners;
    private final Scheduler scheduler;
    public EnqueueService(Map<String, JobRunner> jobRunners, Scheduler scheduler) {
        this.jobRunners = jobRunners;
        this.scheduler = scheduler;
    }

    public String enqueueJob(String jobName, Map<String, String> jobParameters) {
        logger.info("Enqueueing job {} with parameters {}", jobName, jobParameters);
        JobRunner jobRunner = jobRunners.get(jobName);
        String jobId = UUID.randomUUID().toString();

        OneTimeTask<Void> foo = Tasks.oneTime("foo").execute((instance, ctx) -> {
            jobRunner.execute(jobParameters);
        });

        scheduler.schedule(foo.instance(jobId), Instant.now().plusSeconds(5));

        return jobId;
    }

I see the task created on the db, I also see it changing from picked = false to true. But it is never executed.

I wonder if this is related to timezone, but it is hard to believe that since the task gets picked up, the date on DB is in UTC and my machine is in EST.

Any ideas why this task is not being executed? Any pointers on how to debug and figure it out?

Thank you

[viniciusccarvalho]

Ok I do see this line in the logs:

Failed to find implementation for task with name 'foo'. Execution will be excluded from due. The scheduler normally delete unresolved tasks after 14d. To handle manually, either delete the execution from the database, or add an implementation for it.

After enabling debug. I was looking at the examples for Boot, and I found a bit odd that one needs to register the oneOf task beans. If I may offer a constructive feedback. Would be nice to make that a bit more clear on the docs, if indeed we need tasks to be registered as beans so that the scheduler can have them registered.

Is there an alternative to this?

[viniciusccarvalho]

So I got the task to be executed by creating a bean. I also have a recurring task that simply stopped executing.

 @Bean
    public RecurringTask<Void> minuteTestTask() {
        return Tasks.recurring("minute-test", Schedules.fixedDelay(Duration.ofMinutes(1))).execute((instance, ctx) -> {
            System.out.println("Running minute test task");
        });
    }

For some reason it no longer executes, when I query the table I see that the entry version is constantly updated, but the task is never ran :(

No clue on what is going on, any hints?

[viniciusccarvalho]

After wiping the database entry the task seems to be running again, but this seems strange, there were no warnings, and the data seems to be the exact same on the table, the columns execution_time and last_success are updated just like before, but now the task actually runs ...