Investigate Failed Operations
The IoT.live Portal provides several tools to help identify, investigate, and resolve failed operational actions across devices, batch workflows, and provider integrations.
Failed operations can occur due to:
- Provider validation errors
- Unsupported device states
- Invalid data
- Permission restrictions
- Synchronisation delays
- Connectivity or subscription issues
[IMAGE PLACEHOLDER: Failed operations overview]
Identify failed operations
Operational failures may appear within:
- Batch Operations
- Audit Trail
- Inventory Management
- eSIM workflows
- Provider synchronisation status
Common indicators include:
- Failed status messages
- Partial success notifications
- Validation warnings
- Provider error responses
[IMAGE PLACEHOLDER: Failed operation indicators]
Review Batch Operations
For bulk workflows, start by reviewing the Batch Operations module.
To investigate a failed batch job:
- Open Batch Operations
- Locate the affected job
- Open the job details view
- Review failed records and validation messages
[IMAGE PLACEHOLDER: Batch job failure details]
Common batch failure causes include:
- Invalid device identifiers
- Unsupported rate plans
- Missing attributes
- Provider-side restrictions
- Upload formatting issues
Review Audit Trail activity
Use the Audit Trail module to investigate:
- User-triggered actions
- Failed operational updates
- Device lifecycle changes
- Administrative activity
- Synchronisation events
[IMAGE PLACEHOLDER: Audit Trail investigation]
Audit records can help identify:
- Who initiated the action
- When the operation occurred
- Which devices were affected
- Whether provider responses were returned
Review device-level information
If the issue affects a single device:
- Open Inventory Management
- Locate the device
- Review the device details page
- Run diagnostics if required
[IMAGE PLACEHOLDER: Device troubleshooting workflow]
Review:
- Native mode
- Provider information
- Usage activity
- Assigned rate plans
- Tags and attributes
- eSIM status
Check provider synchronisation
Some failures may result from delayed provider synchronisation rather than permanent operational errors.
Temporary delays may affect:
- Status updates
- Usage visibility
- eSIM operations
- Lifecycle transitions
- Rate plan changes
[IMAGE PLACEHOLDER: Provider synchronisation delay]
Synchronisation timing varies between connectivity providers.
Common operational failure scenarios
Scenario | Recommended Action |
|---|---|
Rate plan update failed | Validate provider support and plan availability |
Native mode change incomplete | Review provider synchronisation status |
eSIM migration failed | Verify profile compatibility and subscription state |
Batch upload rejected | Review CSV formatting and identifiers |
Device missing from results | Check filters, account scope, and tags |
Export operational evidence
When escalating issues, export relevant:
- Batch job results
- Audit records
- Device information
- Validation messages
- Operational screenshots
[IMAGE PLACEHOLDER: Export troubleshooting evidence]
Capturing failed records and provider responses early can significantly speed up troubleshooting.
Escalate unresolved issues
If the issue cannot be resolved internally:
- Gather affected device identifiers
- Record timestamps and operational actions
- Export validation results
- Capture screenshots and diagnostics
- Include provider information where available
This information can help accelerate support investigations and provider escalations.
Operational exports and audit records may contain sensitive commercial or device information and should be handled securely.