The Jio DLT Platform (Jio TrueConnect) primarily uses the universal DLT error codes (6XX series) mandated by TRAI, along with specific codes in the 7XXX, 8XX, and 5XXX series to detail DLT registration and scrubbing failures.
The error codes are generally categorized by the component that failed verification during the scrubbing process: Entity, Telemarketer (TM), Header (Sender ID), or Template.
1. Universal DLT Scrubbing Codes (6XX Series)
These codes are common across all Indian DLT platforms, including Jio's.Export to Sheets
| Error Code |
Status Name |
Jio DLT Description |
| 601 | ENTITY_NOT_REGISTERED | No entry of the Principal Entity (PE) on the platform (or is inactive). |
| 603 | ENTITY_BLACKLISTED | The entity is blacklisted on all DLT Platforms. |
| 610 | TELEMARKETER_NOT_REGISTERED | The associated Telemarketer (TM) ID is not registered or active. |
| 620 | HEADER_NOT_FOUND | No record found with the submitted Header (Sender ID). |
| 623 | PEID_NOT_MATCHED_WITH_HEADER | The PEID is not linked to the Header used for the message. |
| 630 | TEMPLATE_NOT_FOUND | No record found with the submitted Template ID. |
| 633 | TEMPLATE_NOT_MATCHED | The submitted message content does not exactly match the approved DLT template (most common error). |
| 634 | HEADER_NOT_REGISTERED_FOR_TEMPLATE | The Header is not linked/registered for use with the Template ID. |
| 635 | TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH | The value in a variable ({#var#}) exceeded the maximum allowed length (usually 30 characters). |
| 650 | PREFERENCE_NOT_MATCHED | Message blocked due to recipient DND/preference settings. |
| 651 | INVALID_PROMO_TIME | Promotional message blocked outside of permitted hours (9 PM to 10 AM). |
| 670 | SCRUBBING_FAILED | General DLT system exception or failure during the scrubbing process. |
2. Jio-Specific DLT Linkage & Status Codes
Jio (and other operators) often use these specific codes to detail errors related to the Entity/Telemarketer relationship and database checks.
| Error Code |
Status Name |
Jio DLT Description |
| 7001 | Entity is inactive | Entity is inactive on the platform (Alternative to 602). |
| 7003 | Entity not in DB | Entity not found in the DLT database (Alternative to 601). |
| 812 | Missing PE-TM Hash in Aerospike | The crucial linkage/hash between your Principal Entity (PE) and your Telemarketer (TM) is missing in the database. |
| 813 | PE ID Mismatch | The PE ID submitted in the request does not match the PE ID linked to the TM Hash. |
3. Jio Mapping & Detailed DLT Codes (5XXX Series)
| Error Code |
Status Name |
Jio DLT Description |
| 5101 | FULLY BLOCKED or PROMO BLOCKED | Message blocked due to DND preferences (Similar to 650). |
| 5201 | If Header not active | The Sender ID is inactive (Similar to 621). |
| 5307 | Content not matched | The message content failed the template match (Similar to 633). |
| 5401 | COMM/HEADER Mismatch | Transactional/Service message submitted with an Inactive/Blacklisted Header. |
| 5501 | Consent Not in DB | An explicit consent record for the message is missing. |
Troubleshooting Key Jio Errors
| Error Code |
Root Cause |
Immediate Fix |
| 633 / 5307 | Template Mismatch | Correct the message content. Check for extra spaces, missing punctuation, or case sensitivity in the static text. Ensure dynamic parts use {#var#} exactly. |
| 623 / 813 | Header/PEID Linkage | Log in to the Jio TrueConnect portal. Ensure the Header (Sender ID) is approved and correctly mapped to your Principal Entity ID. |
| 812 | PE-TM Linkage | Request your messaging service provider (Telemarketer) to re-map/re-link your Principal Entity ID on the Jio DLT portal. |
