Workflow | Monitor eSIM status in Digi Remote Manager

Use Digi Remote Manager to monitor eSIM status by confirming that a carrier profile has been successfully obtained, that the device is connected to the cellular network using the intended profile, and .

Check to see that you have the necessary activation codes.

Action	Considerations
Add activation codes to Digi Remote Manager, if needed. Check the status of your available activation codes on the Activation Codes tab. Update the information for an activation code, if needed. Add an activation code to a device so it downloads the associated carrier profile. To maintain an up-to-date list, delete activation codes, as needed.	Downloaded ≠ actively used: A device may have obtained a profile but be using a different one (or not connected). Available ≠ ready to connect: It only means the code hasn’t been used yet. Failed indicates an attempt didn’t complete: It signals a processing issue, not the exact cause. Track codes as single-use assets: Once used, don’t assume the same code can be reused for another device. Keep bulk-upload data clean: Use a valid SPN Service Provider Name for carrier and avoid formatting issues that can cause errors or confusion. Consider timing: A code may remain Available until a device actually attempts the download; temporary conditions can also trigger Failed.

Action

Considerations

Add activation codes to Digi Remote Manager, if needed. Check the status of your available activation codes on the Activation Codes tab.

Update the information for an activation code, if needed.

Add an activation code to a device so it downloads the associated carrier profile.

To maintain an up-to-date list, delete activation codes, as needed.

Downloaded ≠ actively used: A device may have obtained a profile but be using a different one (or not connected).
Available ≠ ready to connect: It only means the code hasn’t been used yet.
Failed indicates an attempt didn’t complete: It signals a processing issue, not the exact cause.
Track codes as single-use assets: Once used, don’t assume the same code can be reused for another device.
Keep bulk-upload data clean: Use a valid SPN Service Provider Name for carrier and avoid formatting issues that can cause errors or confusion.
Consider timing: A code may remain Available until a device actually attempts the download; temporary conditions can also trigger Failed.

Confirm the device is connected using that desired carrier profile.

Action	Considerations
View the list of carrier profiles on all devices to see what profiles exist in your account and manage them for provisioning and troubleshooting. View a list of carrier profiles on one device to see what profiles the device has available as well as confirm the one that it is actively using. If the device does not have the desired carrier profile, add the activation code.	Downloaded ≠ actively used: A device may have obtained a carrier profile but be using a different one (or not connected). Separate “profile” from “connection.” The right profile can be chosen but still fail due to coverage, APN, or service issues. Watch for failover behavior. Devices with multiple profiles may connect using a backup profile instead. Connectivity can be temporary. A device may switch profiles during recovery or configuration changes. Activation code status isn’t proof of usage. “Downloaded” confirms the profile was obtained, not that it’s currently being used.

Action

Considerations

View the list of carrier profiles on all devices to see what profiles exist in your account and manage them for provisioning and troubleshooting.

View a list of carrier profiles on one device to see what profiles the device has available as well as confirm the one that it is actively using.

If the device does not have the desired carrier profile, add the activation code.

Downloaded ≠ actively used: A device may have obtained a carrier profile but be using a different one (or not connected).
Separate “profile” from “connection.” The right profile can be chosen but still fail due to coverage, APN, or service issues.
Watch for failover behavior. Devices with multiple profiles may connect using a backup profile instead.
Connectivity can be temporary. A device may switch profiles during recovery or configuration changes.
Activation code status isn’t proof of usage. “Downloaded” confirms the profile was obtained, not that it’s currently being used.

Check cellular registration and data connectivity for a device.

Action	Considerations
Navigate to the dashboard for a device (SIM Management and Connections) to confirm the device is registered on the cellular network and passing traffic; this helps distinguish “profile present” from “service working.”	Registration ≠ usable data. A device can be “registered” to the network but still fail to pass traffic (for example due to plan status, routing, or APN settings). Confirm the intended profile is active. If multiple profiles exist, the device may register using a different profile than expected (especially with failover setups). Check the APN requirement. Some carriers require a specific APN; the wrong APN can allow partial attachment/registration but block data sessions. Allow for activation timing. Newly downloaded/activated profiles may take time to fully provision on the carrier side, and devices may need to reattach after profile changes. Signal quality matters. Weak signal can cause intermittent registration, frequent drops, or slow/failed data even if the profile is correct. Coverage and roaming constraints can block data. A device may register to a partner network but have limited or no data allowed depending on the plan. Don’t rely only on one indicator. Validate connectivity with more than one check (e.g., registration status + IP address + a simple reachability test). Device network path still applies. If the device has firewall rules, VPN/tunnel settings, or routing policies, those can prevent traffic even when cellular is up. “Downloaded” activation code status doesn’t confirm connectivity. It only confirms the profile was obtained, not that registration and data are currently working.

Action

Considerations

Navigate to the dashboard for a device (SIM Management and Connections) to confirm the device is registered on the cellular network and passing traffic; this helps distinguish “profile present” from “service working.”

Registration ≠ usable data. A device can be “registered” to the network but still fail to pass traffic (for example due to plan status, routing, or APN settings).
Confirm the intended profile is active. If multiple profiles exist, the device may register using a different profile than expected (especially with failover setups).
Check the APN requirement. Some carriers require a specific APN; the wrong APN can allow partial attachment/registration but block data sessions.
Allow for activation timing. Newly downloaded/activated profiles may take time to fully provision on the carrier side, and devices may need to reattach after profile changes.
Signal quality matters. Weak signal can cause intermittent registration, frequent drops, or slow/failed data even if the profile is correct.
Coverage and roaming constraints can block data. A device may register to a partner network but have limited or no data allowed depending on the plan.
Don’t rely only on one indicator. Validate connectivity with more than one check (e.g., registration status + IP address + a simple reachability test).
Device network path still applies. If the device has firewall rules, VPN/tunnel settings, or routing policies, those can prevent traffic even when cellular is up.
“Downloaded” activation code status doesn’t confirm connectivity. It only confirms the profile was obtained, not that registration and data are currently working.

You have finished viewing the eSIM setup in Digi Remote Manager by confirming activation code status, profile availability, and cellular registration/data connectivity. Continue monitoring in Digi Remote Manager to verify the intended profile is in use and to catch connectivity issues early.