> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/shopware/shopware6_en_us/automation-and-schedules/job-queue-entries.md).

# Job Queue Entries

Automate your Shopware synchronization with Job Queue Entries.

The Job Queue in Business Central lets you run synchronization tasks automatically according to a defined schedule.

## 1. Available Tasks

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Order download</strong></td><td>Imports new orders from Shopware</td></tr><tr><td><strong>Item upload</strong></td><td>Synchronizes item data to Shopware</td></tr><tr><td><strong>Price upload</strong></td><td>Updates prices in Shopware</td></tr><tr><td><strong>Inventory upload</strong></td><td>Synchronizes inventory levels</td></tr><tr><td><strong>Category upload</strong></td><td>Updates categories</td></tr><tr><td><strong>Picture upload</strong></td><td>Transfers item pictures</td></tr></tbody></table>

## 2. Creating a Job Queue Entry

{% stepper %}
{% step %}
Open *Job Queue Entries* in Business Central.
{% endstep %}

{% step %}
Click "+New".

<div align="left" data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/KGkV6FvH09CI6tQjWevB/Bildschirmfoto%202026-06-29%20um%2010.37.37.png" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Fill in the fields:
{% endstep %}
{% endstepper %}

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Object Type to Run</strong></td><td>Codeunit</td></tr><tr><td><strong>Object ID to Run</strong></td><td>ID of the Shopware codeunit</td></tr><tr><td><strong>Description</strong></td><td>for example "Shopware Order Import"</td></tr><tr><td><strong>Earliest Start Date/Time</strong></td><td>Date/time</td></tr><tr><td><strong>Job Timeout</strong></td><td>Interval</td></tr><tr><td><strong>Recurrence</strong></td><td>Days of the week on which the entry runs.</td></tr></tbody></table>

<details>

<summary><strong>Scheduling examples</strong></summary>

<table><thead><tr><th width="153.347900390625">Task</th><th width="189.2579345703125">Recommended interval</th></tr></thead><tbody><tr><td>Order download</td><td>15-30 minutes</td></tr><tr><td>Inventory upload</td><td>30-60 minutes</td></tr><tr><td>Price upload</td><td>Once daily</td></tr><tr><td>Item upload</td><td>Once daily</td></tr></tbody></table>

</details>

<div align="left" data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/lv9lWm9mmaYmslQVARTT/Bildschirmfoto%202026-06-29%20um%2010.47.22_.png" alt="" width="563"><figcaption></figcaption></figure></div>

## 3. Activating a Job Queue Entry

### Changing the status

{% columns %}
{% column %}
{% stepper %}
{% step %}
Select the entry.
{% endstep %}

{% step %}
Click "Set Status to Ready".
{% endstep %}

{% step %}
The entry runs at the next interval.
{% endstep %}
{% endstepper %}
{% endcolumn %}

{% column %}

<figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/p7ZKLdxSbt2u82G2F3om/Bildschirmfoto%202026-06-29%20um%2010.50.45.png" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

<details>

<summary><strong>Status overview</strong></summary>

<table><thead><tr><th width="163.5137939453125">Status</th><th width="329.276611328125">Description</th></tr></thead><tbody><tr><td><strong>In Queue</strong></td><td>Waiting for the next run</td></tr><tr><td><strong>Ready</strong></td><td>Runs at the next interval</td></tr><tr><td><strong>In Process</strong></td><td>Currently running</td></tr><tr><td><strong>Error</strong></td><td>Error during the last run</td></tr><tr><td><strong>On Hold</strong></td><td>Stopped manually</td></tr></tbody></table>

</details>

## 4. Logging

### 4.1 Execution log

1. Open the **Job Queue Entry**
2. Click the three dots *"..."* <i class="fa-right">:right:</i> *"Log Entries"*
3. You see all runs with their status and duration.

<div align="left"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/lVnNyBk6r91xHVweb0qO/Bildschirmfoto%202026-06-29%20um%2011.01.27.png" alt=""><figcaption></figcaption></figure> <figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/EyqojjRNvoadAJBUOvoV/Bildschirmfoto%202026-06-29%20um%2011.08.17.png" alt=""><figcaption></figcaption></figure></div>

### 4.2 Error analysis

Proceed as described under [*"4.1 Execution log"*](#id-4.1-execution-log) and then click *"Show Error Message"* in the menu, or open the *Job Queue Entries* page directly and click the three dots *"..."* <i class="fa-right">:right:</i> *"Show Error".*

Analyze the cause, or accept the *"Recommended Action \[...]"*, for example.

<div align="left" data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/7Ixh6VvLr58QKDrKZU8P/Bildschirmfoto%202026-06-29%20um%2011.11.38.png" alt="" width="563"><figcaption></figcaption></figure></div>

## 5. Example Configuration

{% tabs %}
{% tab title="Order download" %}

```
Object Type to Run: Codeunit
Object ID to Run: [Order download codeunit ID]
Description: Shopware - Download Orders
No. of Minutes between Runs: 15
Run on Days of the Week: Mon-Sun
```

every 15 minutes
{% endtab %}

{% tab title="Inventory upload" %}

<pre><code><strong>Object Type to Run: Codeunit
</strong>Object ID to Run: [Inventory upload codeunit ID]
Description: Shopware - Synchronize Inventory
No. of Minutes between Runs: 60
Run on Days of the Week: Mon-Sun
</code></pre>

hourly
{% endtab %}

{% tab title="Price upload" %}

```
Object Type to Run: Codeunit
Object ID to Run: [Price upload codeunit ID]
Description: Shopware - Synchronize Prices
Earliest Start Time: 06:00:00
No. of Minutes between Runs: 1440 (= 24 hours)
Run on Days of the Week: Mon-Sun
```

daily at 6:00 AM
{% endtab %}
{% endtabs %}

<details>

<summary><strong>Tips for day-to-day use</strong></summary>

#### Scheduling

* Distribute tasks throughout the day.
* Avoid overlaps.
* Schedule resource-intensive tasks at night.

#### Monitoring

* Check the logs regularly.
* Set up notifications for errors.
* Respond to problems quickly.

#### Performance

* Limit the number of concurrent tasks.
* Optimize data volumes.
* Use filters for incremental updates.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/shopware/shopware6_en_us/automation-and-schedules/job-queue-entries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.