---
title: "Managing Update Jobs"
slug: "managing-update-jobs"
description: "Manage firmware, configs, and containers with Update Jobs in iRM Cloud - schedule rollouts, track status, and ensure compliance across industrial router fleets."
tags: ["icom Router Management", "iRM"]
updated: 2025-09-01T15:08:11Z
published: 2025-09-16T07:00:05Z
canonical: "docs.insys-icom.com/managing-update-jobs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Update Jobs

Update jobs are the primary method for distributing data to routers via icom Router Management Cloud. They enable centralized management of firmware, configurations, and applications across entire fleets, supporting compliance with operational and security policies.

Update jobs rely on *Update Packages*, which are structured archives containing firmware, configurations, containers, and more. If you are not yet familiar with update packages, refer to the article [Using Update Packages](/kb/docs/using-update-packages).

> [!NOTE]
> Note
> 
> Update Jobs are only available in **icom Router Management Cloud** and require a valid “**Basic**” plan license.

---

## What Are Update Jobs

An update job in icom Router Management Cloud defines:

- Which routers should receive an update
- Which update package should be deployed
- When the update should be executed

Update Jobs are created in the following situations:

1. **Firmware update** – when you want to deploy a new firmware version to one or more routers.
2. **Custom update package** – when you want to deploy containers, container storage, licenses, or certificates.
3. **Configuration template** – when you want to roll out router or container configuration templates.

Update jobs provide:

- Full visibility into the rollout process
- Structured management of updates over time
- Traceability and control critical for cybersecurity and regulatory compliance (e.g., CRA, IEC 62443)

---

## Overview of the Update Jobs Page

Navigate to ***Update Management → Update Jobs*** to access the overview. The page displays a table listing all created update jobs, including:

- **Name/Update**: The name of the Update Job and the file name of the included Update Package
- **Routers**: How many routers are assigned to the job
- **Created At**: When the job was created
- **Executed At**: When the job was executed (if applicable)
- **Status:** Such as *Successfully Executed*, *Active, Failed, or Ready* (waiting to be executed)

![](https://cdn.document360.io/c690fe99-a3eb-474c-a449-c2c75e5df119/Images/Documentation/Update Jobs Overview(1).png)

---

## Creating a New Update Job

### a) From the Router List

1. Go to **Inventory → Routers**.
2. Select one or more routers.
3. Open the **Select action** menu.
4. Choose one of the following:
  - **Update firmware**
  - **Deploy update package**
  - **Apply configuration template**
5. Configure the job details.

---

### b) From the Firmware Page

1. Go to **Update Management → Firmware**.
2. Select the desired firmware version.
3. Choose the router(s) you want to deploy it to.
4. Confirm to create the Update Job.

---

### c) From the Update Packages Page

1. Go to **Package Management → Update Packages**.
2. Select the update package you want to deploy.
3. Choose the router(s) you want to deploy it to.
4. Confirm to create the Update Job.

> [!NOTE]
> Each created Update Job appears on the Update Jobs page.
> 
> If you select **Start manually later**, the job is created but not executed immediately. Until execution, the job remains editable (e.g., change router selection, timing, or options).

---

## Managing Existing Update Jobs

Update Jobs in icom Router Management represent scheduled or executed deployments. How you can interact with a job depends on its **status**.

### Executed Jobs (immutable)

- **Read-only**: Once a job has been executed, it cannot be changed anymore.
- **Details available**:
  - Included routers
  - Timestamps (created, updated, executed)
  - Update package or configuration applied
  - Execution results (success/failure per router)

![](https://cdn.document360.io/c690fe99-a3eb-474c-a449-c2c75e5df119/Images/Documentation/Update Job Details Executed.png)

---

### Jobs in Status *Ready* (editable)

Jobs in status *Ready* are created but not yet executed. These jobs can still be modified.

**Editable properties:**

- **Job name**
- **Job description**
- **Target routers** (add or remove devices)

---

## Special Cases by Job Type

### Configuration Deployment (Router or Container Config)

- **Configuration template**: Cannot be changed to a different template.
- **ASCII Values tab**:
  - Edit string parameters directly (inline editing).
  - Alternatively, upload an Excel file with parameter values.

![](https://cdn.document360.io/c690fe99-a3eb-474c-a449-c2c75e5df119/Images/Documentation/Update Jobs Details Edit ASCII Values.png)

---

### Update Package Deployment

- In the job details page, click the **pencil icon** next to the field **Update**.
- Select a different package:
  - Custom update packages you uploaded.
  - Official INSYS icom firmware packages.

![](https://cdn.document360.io/c690fe99-a3eb-474c-a449-c2c75e5df119/Images/Documentation/Update Jobs Details Change Package.png)

---

## Executing a Job

There are two ways to execute jobs in status *Ready*:

### From the Update Jobs Page

1. Navigate to **Update Jobs**.
2. Select a single job.
3. Open the **Select action** menu.
4. Click **Execute now**.

---

### From the Job Details Page

1. Open the details of a job in status *Ready*.
2. Click the **Execute now** button in the upper section.

---

## Re-executing Completed Jobs

For jobs that have already been executed, the details page provides a **Run again** button.

- This is particularly useful if the job was only **partially successful** (e.g., some routers updated correctly, others failed).
- When re-running, the same parameters (package, configuration, routers) are applied again.