> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/infinity/sim-estate-management/how-to-create-bulk-jobs.md).

# How to create bulk jobs

## Overview

Bulk Operations in the Infinity Portal allow you to make changes to multiple SIMs at the same time rather than updating each SIM individually.

Bulk jobs can be used for operations including:

* SIM activation and termination
* SIM suspension and unsuspension
* Package changes
* Portfolio changes
* Friendly name updates
* Group assignments
* IMEI and other SIM attribute updates

{% hint style="info" %}
The available options will depend on your Infinity access and permissions. Portfolio Admin and Support Specialist are roles commonly associated with access to Bulk Operations.
{% endhint %}

## Accessing Bulk Operations

1. Log in to the Eseye Infinity Portal.
2. From the main navigation menu, select **Bulk Operations**.
3. Select **Create Job**.
4. Choose the type of bulk operation you want to perform.
5. Infinity will then provide the appropriate CSV template for that operation.

## Creating a Bulk Job

The general process is:

**Bulk Operations** > **Create Job** > Select Job Type > Download CSV > Populate CSV > Upload > **Continue**

<figure><img src="https://3553167287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXGhN6gzyULR0TDJArp4a%2Fuploads%2FOG6NpmbO8IwtOqnpeSiC%2Finfinity-bulk-jobs-type.png?alt=media&amp;token=8a771f51-9a26-4de5-938e-82deb032de14" alt="Bulk Operations page with the Select job type list open, showing job types such as ICC Package Update, ICC Status Change and ICC Suspension Change"><figcaption><p>Select job type</p></figcaption></figure>

### Step 1: Select the job type

Choose the operation you want to perform.

| Requirement                 | Bulk Job                              |
| --------------------------- | ------------------------------------- |
| Activate or terminate SIMs  | `ICC Status Change`                   |
| Suspend or unsuspend SIMs   | `ICC Suspension Change`               |
| Change a package            | `ICC Package Update`                  |
| Update friendly names       | `ICC Update Attribute - friendlyName` |
| Update groups or attributes | Appropriate Attribute Update          |

{% hint style="warning" %}
Important: Use the correct bulk-job type for the change you are making. Do not combine unrelated changes into the same CSV.
{% endhint %}

## Download the CSV Template

* Once you have selected the operation, download the CSV template provided by Infinity

  <figure><img src="https://3553167287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXGhN6gzyULR0TDJArp4a%2Fuploads%2Fgit-blob-47fb478a8e491549dc4ff22cb9760d8c64bc7a9b%2Finfinity-bulk-jobs-user-guide-02.png?alt=media" alt="Notice listing the CSV columns the uploaded file must have, with a Download button for the template"><figcaption><p>Download the CSV template</p></figcaption></figure>
* Open the file using Microsoft Excel, LibreOffice Calc or another compatible CSV editor.
* Populate the required SIM information.
* Keep the existing CSV structure.

Using the template supplied for that particular operation helps ensure Infinity receives the data in the expected format.

## Activation and Termination

For bulk activations or terminations:

1. Select **Bulk Operations**.
2. Select **Create Job**.
3. Choose `ICC Status Change`.
4. Download the CSV template.
5. Enter the ICCIDs beginning with 89 into Column C.
6. Enter the required status into Column D.
7. Save the file as a CSV.
8. Return to Infinity and upload the completed file.
9. Select **Continue** to submit the job.

### Status values

* `active` = Activate the SIM
* `available` = Terminate the SIM

The documented CSV structure uses:

* Column A: `update`
* Column B: `icc`
* Column C: ICCID
* Column D: required status

### Example

| Column A (`operation`) | Column B (`entityName`) | Column C (`iccId`)    | Column D (`status`) |
| ---------------------- | ----------------------- | --------------------- | ------------------- |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `active`            |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `active`            |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `available`         |

Values should be entered exactly as expected by the template, including lowercase values where specified.

## Suspension and Unsuspension

1. Go to **Bulk Operations** > **Create Job**.
2. Select `ICC Suspension Change`.
3. Download the CSV.
4. Populate the ICCIDs in Column C.
5. Set the required value in Column D.
6. Save the file as CSV.
7. Upload it back into Infinity.
8. Select **Continue**.

Use:

* `yes` = Suspend
* `no` = Unsuspend

### Example

| Column A (`operation`) | Column B (`entityName`) | Column C (`iccId`)    | Column D (`customerSuspend`) |
| ---------------------- | ----------------------- | --------------------- | ---------------------------- |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `yes`                        |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `no`                         |
| `update`               | `icc`                   | `89xxxxxxxxxxxxxxxxx` | `yes`                        |

## Other Bulk Updates

Infinity also supports bulk updates for other SIM attributes and operations, including package, portfolio, friendly-name and group changes.

For example, a bulk friendly-name update follows:

**Bulk Operations** > **Create Job** > `ICC Update Attribute - friendlyName` > Download CSV > Add ICCIDs/names > Upload CSV > **Continue**

The same general principle applies to the other bulk options: select the required operation first and then use the CSV template Infinity provides for it.

## Keep Different Changes Separate

Where multiple types of changes are required, create separate bulk jobs.

For example, if 100 SIMs need to be:

* Activated
* Moved onto a new package
* Added to a group
* Given friendly names

Create the relevant jobs separately rather than trying to combine all four changes into one CSV. This reduces spreadsheet errors and makes each result easier to monitor and validate.

## Upload and Submit the Job

1. Save the completed file as CSV.
2. Return to the **Bulk Operations** page.
3. Select the upload area.
4. Browse to the completed CSV.
5. Upload the file.
6. Review your selection.
7. Select **Continue**.

Infinity will then queue the bulk job for processing.

## Monitoring the Job

After submission, Infinity provides a Job ID.

For viewing the submitted jobs please navigate using:

**Bulk Operations** > **View Job**

<figure><img src="https://3553167287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXGhN6gzyULR0TDJArp4a%2Fuploads%2Fgit-blob-d2ad3eb0a50da78fadff628f4409f50ee0829175%2Finfinity-bulk-jobs-user-guide-03.png?alt=media" alt="Bulk Operations job list showing Job Id, Name, Job Date, Completed Date, Status, request and response file downloads, and success and failed counts"><figcaption><p>View submitted bulk jobs</p></figcaption></figure>

Use **View Job** to monitor the bulk request. Processing time can vary depending on the number of SIMs included in the job. Once processing has finished, the job should show a **Completed** status.

## Checking the Results

Once the job completes, check:

* Job status
* Success count
* Failure count

Example: if you submitted 100 SIMs, the result might show Success: 98 and Failed: 2.

{% hint style="warning" %}
Do not assume that a completed job means every individual SIM update succeeded. If failures are reported, select **Response** to identify the affected records and review the result returned for them.
{% endhint %}

## Handling Failures

1. Open the completed job.
2. Check the failure count.
3. Select **Response**.
4. Identify which SIMs failed.
5. Review the returned information.
6. Confirm the ICCID and requested values in the original CSV.
7. If required, correct the issue and process the affected SIMs again.
8. If the cause cannot be identified, raise the issue with Eseye Support.

Where failures require further investigation, contact <support@eseye.com> and provide the Job ID, original CSV and the relevant response details.

## Good Practice

Before submitting a large bulk job:

* Use the CSV template supplied by Infinity.
* Confirm you are using the correct job type.
* Check the ICCIDs carefully.
* Do not alter the template structure unnecessarily.
* Use the exact values expected by the selected operation.
* Keep different types of updates in separate jobs.
* Retain the original CSV until processing has completed.
* Record the Job ID for significant customer or operational changes.
* Always check the success and failure counts after completion.

{% hint style="info" %}
For particularly large or business-critical changes, validate the change against a small number of SIMs first where operationally appropriate before submitting the full estate.
{% endhint %}

## Quick Reference

| Stage    | Path / Action                                                                                                   |
| -------- | --------------------------------------------------------------------------------------------------------------- |
| Create   | Infinity > Bulk Operations > Create Job > Select Operation > Download CSV > Populate > Save > Upload > Continue |
| Monitor  | Bulk Operations > View Job > Job ID > Status                                                                    |
| Validate | Completed > Check Success Count > Check Failure Count > Response                                                |

## Support Information

If a failed record cannot be resolved from the response details, contact Eseye Support and include:

* The Infinity Job ID
* The bulk operation type
* The original CSV file
* The affected ICCIDs
* The error or response details
* The date and approximate time the job was submitted


---

# 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.eseye.com/infinity/sim-estate-management/how-to-create-bulk-jobs.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.
