Talend job fails due to an execution already in pending or running status as per Talend Management Console

Lusemar_Oliveira — Wed, 02 Sep 2026 08:42:08 GMT

A Talend job scheduled to run every day at the same time fails because Talend Management Console (TMC) detects that the same plan already has an execution in Pending or Running status.

This occurs when the plan is configured to disallow overlapping executions. The Talend Management Console prevents the new execution from starting while the previous execution is still active.

Resolution

If concurrent executions are safe and intended for the job:

Open Talend Management Console.
Navigate to the affected plan.
Open the plan's Details page and click Edit.
Open the Schedule section.
Enable Allow parallel run of this plan.
Save the plan configuration.

If parallel execution is not appropriate, keep the option disabled and review the schedule and execution duration. As a best practice, leave at least a one-minute margin between the expected completion of one execution and the start of the next scheduled execution.

Also verify whether any previous executions are unnecessarily remaining in Pending status and investigate the underlying job or Remote Engine capacity if applicable.

For additional information, see Talend Management Console – Scheduling plans.

Cause

The scheduled plan does not allow parallel executions, and the previous execution has not completed when the next scheduled trigger occurs.

This can happen when:

The job execution takes longer than expected.
A previous execution remains in Pending or Running status.
The schedule interval does not provide sufficient time for the previous execution to finish.

Environment

Talend Cloud
Talend Management Console

article Talend job fails due to an execution already in pending or running status as per Talend Management Console in Official Support Articles

Talend job fails due to an execution already in pending or running status as per Talend Management Console

Resolution

Cause

Environment