Skip to main content Skip to complementary content

Debugging Job tasks

You can run a manually triggered Job again in debug mode to identify possible bugs.

Before you begin

Running a Job task in debug mode is only possible if the task is not in Pending or Running status.

Procedure

  1. Access the Run overview page of the failed Job.
    You can access this page:
    • From the task details page, expand the run in the Last 5 runs section and click Logs.
    • From the Operations page, expand the run and click Logs.
  2. In the top-right corner, click Debug.
    The task is run again, displaying debug level information in the logs. Logs refresh automatically and it may take some time depending on the remote engine.

    In the debug run, all logs are included (from lowest to highest): Debug, Info, Warning, Error, and Fatal.

    By default, Fatal errors are displayed as Error logs. To make it explicitly displayed as Fatal logs in Talend Management Console, ensure that the job.log.fatal.level parameter is present in the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.jobserver.client.cfg file and its value is true.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!