Task triggering and execution issues

Task execution timeout

Problem

A TIMEOUT error occurs.

Cause

The client timed out during processing.

Solution

• Check whether the timeout duration is set too low.

  Set a reasonable timeout duration based on the actual execution time of the task.

• Check the client error log common-error.log.

Custom parameter does not exist

Problem

A javax.el.PropertyNotFoundException: Cannot find property ${property_name} error occurs.

Cause

The custom parameter specified in the condition of the task topology does not exist.

Solution

Check whether the condition matches the list of custom parameters in the task topology configuration. If they do not match, correct the configuration.

Client is not registered with the server

Problem

One of the following errors occurs:

• no targets was found

• target zone is null

• no available target zones was found, please check if clients are available

• no available targets was found in zone

Cause

The client is not registered with the server.

Solution

1. Confirm that the client is running.

   Confirm that the application name and executor name in the console match the client code. Check whether the endpoint configuration is correct.

2. If the client is running, check the common-default.log and common-error.log files in the logs/scheduler directory.

3. If the error logs do not show any errors, check the health check log to confirm that the health check passed.

Client did not provide an executor

Problem

A no suitable job handler for {handler_name} error occurs.

Cause

The handler executor that the task uses exists but is not found in the task's application.

Solution

1. Check whether the handlerName return value in the code matches the executor name in the task configuration.

2. Add a handler implementation to the client. Set the getName value to the current {handler_name}.

Topology has no executable published version

Problem

The 'No published topology process was found' error is reported.

Cause

The topology task was executed, but the topology graph does not have a published version.

Solution

You can edit the topology graph and publish a version.

Server-side exception

Problem

• All tasks in the application fail to trigger.

• The console displays the following failure reason: Server exception when invoke with callback. Please check the server log!

Cause

The project is missing the Tracer dependency:

<dependency>
      <groupId>com.alipay.sofa</groupId>
      <artifactId>tracer-enterprise-sofa-boot-starter</artifactId>
</dependency>

Solution

• Check the pom.xml file of the project for the Tracer dependency. If the dependency is missing, add it manually.

• For projects developed with the SOFABoot framework, confirm whether the SOFABoot version is earlier than 3.4.3.

  • If the version is earlier than 3.4.3, add the Tracer dependency manually.

  • SOFABoot 3.4.3 and later automatically include the Tracer dependency. You do not need to add it manually.

  • For more information about SOFABoot versions, see Version Guide.

Task execution fails due to mutual exclusion

Problem

One of the following errors occurs:

• job is exclusive

• can not be triggered, please check the value of timeoutStrategy and isExclusive

Cause

• A mutually exclusive task is running and cannot be triggered again.

• A mutually exclusive task has timed out and has not been reset. Therefore, it cannot be triggered again.

Solution

You can check the scheduling records:

• If the task is running, wait for it to finish before you trigger it again.

• If a trigger timeout record exists, reset the record to a Success or Failed status. Then, you can trigger the task again.

Task is in a disabled state

Problem

The task has a retry policy configured, but it does not retry after a failure occurs.

Cause

The retry policy works only when the task is enabled. A disabled task does not retry after a failure.

Solution

1. Log on to the Task Scheduling console.

2. Click Task Configuration, and then enable the task in the task list.

Task trigger interval is too short

Symptoms

The following error occurs: the interval for tasks of type callback must be more than 5 minutes.

Cause

For CALLBACK tasks triggered by a Cron expression, the interval between triggers must be more than 5 minutes.

Solution

Modify the Cron expression to make the trigger interval longer than 5 minutes. For example, you can use 1 0/5 * * * ?. For more information about Cron expressions, see CRON Expression Details.

A cluster task with a split processor fails to trigger even when clients are online

This issue occurs because the communication method for the cluster task is set to one-way (ONEWAY), which causes the trigger to fail.

Client task execution fails

Problem

The console shows that the execution failed.

Cause

The client connection cannot be found or the client is abnormal.

Solution

Based on the error message, check the common-error.log file in the logs/scheduler directory of the client.

Task Scheduling cannot find a message task by application name

Cause

The getAllApps method of com.alipay.antscheduler.facade.IAntJobFacade in Antscheduler restricts the search.

Solution

You can upgrade MS to version 2.26.0 or later.

Message-based scheduled task cannot be triggered on a schedule or manually

Symptoms

The following error occurs: send msg error.

Cause

The client is offline.

Solution

Task Scheduling task creation fails

Symptoms

When you create a task, the page displays the following error: Task name already exists.

Cause

A task with the same name may have been created and then moved to the recycle bin.

Solution

Do not reuse task names, even for tasks that have been deleted.

Why does task export only support full export?

Only MS version 2.28.4 lets you export selected tasks, but it only supports full import. All other versions support only full export and full import.

Task scheduling trigger fails

You can check the common-error.log file in the home/admin/logs/scheduler directory. If the cause is a full thread pool, you can increase the size of the thread pool.