Batch Operations & eSIM
Why did my batch operation partially fail?
Partial failures occur when some records process successfully while others fail validation or provider processing.
Common causes include:
- Invalid device identifiers
- Unsupported provider operations
- Missing attributes
- Subscription restrictions
- Provider-side validation errors
To investigate:
- Review Batch Operations results
- Check failed records
- Review Audit Trail activity
- Validate upload formatting
[IMAGE PLACEHOLDER: Partial batch failure example]
Why is my batch job still processing?
Large operations may take time depending on:
- Dataset size
- Provider responsiveness
- Synchronisation timing
- Operational complexity
- eSIM processing requirements
Some provider platforms process operational requests asynchronously.
Can I cancel a running batch operation?
Available cancellation options depend on:
- Provider capabilities
- Processing stage
- Operation type
Some operations may already be committed provider-side and cannot be reversed immediately.
What file formats are supported for uploads?
Batch workflows typically support:
- CSV uploads
- Clipboard paste operations
CSV files should:
- Use supported identifiers
- Follow the documented structure
- Avoid unsupported formatting
Why was my upload rejected?
Common upload validation failures include:
- Incorrect column formatting
- Missing required fields
- Unsupported identifiers
- Invalid operational values
- Provider incompatibility
[IMAGE PLACEHOLDER: Upload validation errors]
Test smaller datasets first before processing large production uploads.
Why are my eSIM operations delayed?
eSIM workflows may take additional time due to:
- Provider-side processing
- Device connectivity
- Network availability
- Subscription state
- Profile download timing
Some updates may not appear immediately within the portal.
Why did my eSIM migration fail?
Possible causes include:
- Unsupported device hardware
- Invalid target profile
- Provider restrictions
- Connectivity interruption
- Subscription incompatibility
To investigate:
- Review Batch Operations results
- Check Audit Trail events
- Validate provider support
- Confirm profile availability
Can I perform eSIM operations in bulk?
Yes. Bulk eSIM operations can be performed using:
- Inventory Management bulk actions
- Batch Operations uploads
- API integrations
Supported workflows may include:
- Profile swaps
- Profile enablement
- Carrier migrations
- Subscription changes
[IMAGE PLACEHOLDER: Bulk eSIM workflow]
Will eSIM operations interrupt connectivity?
Possibly. Some operations may temporarily interrupt:
- Network registration
- Data connectivity
- SMS services
- Subscription availability
Production migrations should be tested on smaller device groups before large-scale rollout.
Why does the portal show different information from the provider platform?
Temporary differences may occur because:
- Synchronisation is still processing
- Provider updates are delayed
- Batch jobs are queued
- Operational updates have not refreshed yet
This is especially common during:
- Large migrations
- Batch operations
- eSIM workflows
- Rate plan updates
Can I retry failed batch records?
Yes. Failed records can typically be:
- Corrected
- Re-uploaded
- Reprocessed in smaller batches
This is often recommended for:
- Validation failures
- Provider-specific errors
- Formatting issues
Re-test failed records in a small validation batch before re-running production operations.
What’s the safest way to run large operational updates?
Recommended best practices include:
- Export affected devices before changes
- Test on smaller pilot groups first
- Validate provider compatibility
- Review rollback procedures
- Monitor Batch Operations during execution
- Review Audit Trail activity after completion
Some provider-side operational changes may apply immediately and affect live production devices.