Manage Job Queue Errors

gear-solid.svg Role Required: Business Central Administrator

When the Bank Connect app is installed, the KXA Update Transaction job queue entry is automatically set up on your Business Central instance. This job queue entry runs on a schedule throughout the day to import bank data into your Bank Account Reconciliation and/or Payment Reconciliation Journals, based on your Automation Settings.

Job queue entries in Business Central may fail for various reasons, such as issues with the server or database, environmental factors like time zone settings, locks and conflicts with other processes, or even simple network hiccups. When this occurs, your Business Central Administrator can update the job queue entry and restart it to continue running on schedule.

If you are not receiving bank data import in your Bank Account Reconciliation and/or Payment Reconciliation Journals, you will see a Job Queue Errors displayed under Bank Connect tiles on the Business Central Dashboard.

 

Please review the Bank Connect Job Error Log to understand why the KXA Update Transactions Job failed. Two common reasons are that the job encountered an error and needs to be restarted, or that it is locked by another user to prevent multiple parallel importing processes. 

Unlock Transaction Import

  1. On the Business Central Dashboard, click on the Bank Connect tile named Job Queue Errors. (Users can also search for "Bank Connect Job Error Log")

  2. On the Bank Connect Job Error Log page, click on the Actions → View Transaction Lock.

  3. On the Transaction Import Lock page, click on the Actions → Unlock Transaction Import.

  4. Click Yes when prompted to confirm the action.

  5. You can now proceed with importing your bank data.

Restarting KXA Update Transactions Job Queue Entry

  1. Use the global search to go to the Job Queue Entries page.

  2. Find the KXA Update Transactions job in the list. The job may have three different statuses:

    • Ready - the job is running as expected; no user action is required
    • On Hold - the job has been paused; the Business Central Administrator will need to restart the job
    • Error - the job is erroring; the Business Central Administrator will need to restart the job

  1. Click on the KXA Update Transactions job to make updates.

    • If the job is running, click the Set On Hold button to pause the job before editing.

  2. Update the fields such as:

    • Earliest Start Date/Time - indicates the earliest date and time for executing the job queue entry.
    • Job run days of the week - outlines the specific days of the week when the job queue entry will be executed.
    • No. of Minutes between Runs - denotes the minimum number of minutes that must pass between the executions of a job queue entry.

  3. Click on the Restart button to save the changes and restart the job.

Add KXA Update Transactions Job Queue Entry

If you don't see the KXA Update Transactions job in the list, you can add the entry manually.

  1. On the Job Queue entries list, click on the +New button to add a new job queue entry.

  2. On the new Job Queue Entry Card, update the following:

    • Object Type to Run → select Codeunit
    • Object ID to Run → type or search for Object ID: 71333583

  3. Optionally, update:

    • Earliest Start Date/Time
    • Run Days
    • No. of Minutes between runs