SchedulerX FAQ

killed from server -- The server terminated the job instance.

don't update progress more than 30s -- An alert triggers when a job instance stops reporting progress for over 30 seconds.

Spring application cannot find the beans -- The Spring container fails to locate the bean specified in your job configuration.

Error: "submit jobInstanceId to worker timeout" -- The scheduler cannot dispatch the job instance to a worker within the expected time.

Error: "used space beyond 90.0%!" -- Disk usage on the worker node exceeds 90%, which prevents the job from running.

Error: "ClassNotFoundException" -- The worker cannot find the class specified in the job configuration. This is usually caused by a packaging or deployment issue.

Error: "jobInstance=xxx don't update progress more than 60s" -- The job instance stops reporting progress for over 60 seconds and is marked as failed.

Job fails with no error message -- The job fails without returning an error. Check execution logs and instance details to diagnose the root cause.

Identify the cause of a job failure -- Trace a failure to its root cause using execution logs and instance details.

Job is stuck during running -- The job enters a running state but never completes.

Troubleshoot slow job execution -- The job completes but takes longer than expected.

Running instances reached the upper limit -- The number of concurrent job instances hits the configured maximum, and new instances are rejected.

Missed schedule: is the job queued or skipped? -- What happens when a job does not complete before the next scheduled trigger: whether the next run is queued or dropped.

View historical records of a one-time job -- How to find execution history for a one-time job after it finishes running.

Perform second-delay scheduling -- Configure jobs to run at second-level intervals with second-delay scheduling.

Job not scheduled at a specific time -- The job does not trigger at the expected time. Check the CRON expression, time zone, and scheduling status.

Set the timeout period -- How to configure the timeout period for a job in SchedulerX.

Job still runs after the instance is stopped -- The job continues to run after the application instance is stopped. Understand why this happens and how to prevent it.

Set advanced configurations for job management -- How to configure advanced job options.

Error: "all workers are busy" -- All available workers are occupied, and no worker can accept the job.

FAQ about job management -- Additional frequently asked questions about job management.

Integrate Tracing Analysis -- How to connect SchedulerX with Tracing Analysis for distributed tracing of job execution.

FAQ about job management -- Additional frequently asked questions about job management.

Job gets stuck or slows down during application release -- A running job stalls or degrades during deployment.

System asks for instance parameters after clicking Run once -- The console prompts for instance parameters after you click Run once. Understand when and how to provide them.

Original Spring timer still runs after SchedulerX takes over -- After migrating scheduled Spring jobs to SchedulerX, the original @Scheduled timer keeps firing. Disable it to avoid duplicate execution.

Get the context for a Spring job -- How to access the SchedulerX job context (such as job parameters and instance ID) within a Spring job.

Does a Spring job return a processing result? -- Whether and how a Spring job can return a result to SchedulerX after execution.

Grant permissions to other accounts -- How to authorize other Alibaba Cloud accounts or RAM users to access your SchedulerX resources.

RAM user lacks permissions to grant permissions to others -- The SchedulerX console shows a permissions error when a RAM user tries to authorize other users. Make sure the RAM user has the required administrative policy attached.

Error: "no worker available" -- No worker is connected to the application group. Check that workers are running and registered to the correct namespace and group.

Error: "DomainNotFoundException" during application release -- The application cannot resolve the SchedulerX service domain during deployment. Verify DNS settings and endpoint configuration.

Error: "can not find namespaceId" during application release -- The configured namespace ID does not match any existing namespace. Verify the ID in the SchedulerX console.

Test local connections in the SchedulerX console -- How to verify that a local development machine can connect to the SchedulerX service.

Local workers cannot connect to the Internet -- Workers on a local machine fail to reach the SchedulerX endpoint. Check firewall rules, proxy settings, and network access.

API throttling policy and rate limits -- The default throttling policy for SchedulerX API operations and how many calls are allowed per minute.

Console error when creating a Kubernetes job via API -- The console reports an error and the page fails to open after you create a Kubernetes job through the API.

Create a workflow via API -- Whether the SchedulerX API supports creating workflows programmatically, and which operations to use.

Specify a worker or label when triggering a stand-alone job via API -- How to target a specific worker or use a job label when calling the API to trigger a job in stand-alone operation mode.

Console error when creating a job via API -- The console reports an error and the page fails to open after you create a job through the API. Check for missing or invalid parameters.