Customs Explorer
⌕

Customs Explorer

ICS2 troubleshooting

ICS2 / TECHNICAL & OPERATIONAL SUPPORT

ICS2 Troubleshooting

Diagnose filing errors. Resolve connection problems. Verify the outcome.

A practical troubleshooting guide for the EU Import Control System 2, covering rejected ENS messages, missing notifications, trader portal access, system-to-system connectivity and uncertain submission status.

VALIDATION ERRORS STI / STP ACCESS AS4 CONNECTIVITY MESSAGE STATUS
Independent educational guidance. Not connected to the European Commission’s ICS2 production system.
ICS2 TROUBLESHOOTING
TECHNICAL DIAGNOSIS / FILING RECOVERY
01 / INITIAL DIAGNOSIS

Find the failure point. Before attempting a fix.

Troubleshooting ICS2 starts by identifying the last confirmed processing event. A failed login, a message transmission timeout, a validation rejection and a missing business notification require different investigations.

Use the checkpoints below to narrow the problem, preserve the evidence and select the correct recovery procedure.

DIAGNOSTIC SEQUENCE

Five checkpoints. One verified outcome.

ILLUSTRATIVE WORKFLOW
01

Access

Can the operator authenticate and use the intended interface?

IDENTITY / AUTHORISATION
02

Transmission

Was the message successfully delivered through the communication channel?

CONNECTIVITY / DELIVERY
03

Validation

Did the message pass the applicable technical and business checks?

SCHEMA / BUSINESS RULES
04

Registration

Is there a confirmed filing result and the relevant references?

FILING / LIFECYCLE
05

Notifications

Were the expected business messages received and processed?

ROUTING / RESPONSE
The checkpoints are a troubleshooting model, not a universal chronological representation of every ICS2 message exchange.
SYMPTOM-BASED TROUBLESHOOTING

Start with what you can observe.

A useful diagnosis connects the visible symptom to the evidence needed to confirm its cause. Do not treat a possible explanation as a confirmed failure.

Observed symptom Possible area First verification Avoid
Cannot sign in to STP UUM&DS access or authorisation Check identity, assigned rights, selected environment and available authentication evidence. Assuming an ICS2 system-wide outage.
STI connection fails Communication channel or technical configuration Review the supported transport configuration, certificates, endpoint and connection logs. Changing declaration data before checking connectivity.
Message is rejected Technical or business validation Retrieve the complete rejection response and identify the reported error. Resending the unchanged message repeatedly.
No filing result received Processing or response delivery Correlate original message identifiers, acknowledgements and available status evidence. Assuming that a timeout proves rejection.
ENS remains incomplete Multiple filing or missing particulars Verify required supplementary filings, registration status and linking references. Assuming that one registered filing completes the ENS.
Expected notification is missing Message routing or recipient configuration Check the intended recipient, communication route and local message processing. Assuming no customs action occurred.
EVIDENCE FIRST

Preserve the original event. Then investigate.

Reliable incident resolution depends on traceable evidence. Before changing the filing or interface configuration, record what was sent, what was received and when the problem occurred.

Important distinction

A Local Reference Number (LRN), a transport message identifier and an MRN serve different purposes. An MRN should only be recorded where it has actually been assigned.

INCIDENT EVIDENCE RECORD CHECKLIST
01
Message identification

Original message ID, LRN where applicable and MRN if assigned.

02
Time and environment

Timestamp, relevant time zone, interface and production or test environment.

03
Original payload

Preserve the submitted message and its relevant technical version.

04
Responses and logs

Technical acknowledgements, business notifications and diagnostic logs.

05
Operational impact

Affected consignment, filing deadline and any outstanding customs instruction.

Retain evidence securely and share only the information necessary for the relevant support investigation.
RECOVERY DECISION

Choose the next action from confirmed evidence.

OUTCOME A

Transmission failure confirmed

Investigate and correct the communication problem. Before retrying, determine whether the original message could have been delivered or processed.

OUTCOME B

Validation rejection confirmed

Correct the identified data or message problem. Use the appropriate submission procedure and confirm the new processing result.

OUTCOME C

Filing registered successfully

Do not create a new original filing merely because a local notification is missing. Investigate response delivery and any outstanding filing issues.

OUTCOME D

Processing status remains uncertain

Reconcile the available references and escalate through the appropriate technical or customs support channel before taking an action that could create a duplicate.

02 / ACCESS & CONNECTIVITY

When ICS2 cannot be reached. Diagnose the connection.

An access failure is not necessarily an ENS filing failure. The cause may lie in user authorisation, certificate configuration, network communication, an AS4 access point or a temporary service interruption.

The first step is to identify how the economic operator connects to ICS2. Portal users and system-to-system senders do not necessarily encounter the same technical problems.

USER-TO-SYSTEM STP

Shared Trader Portal

Browser-based access

Economic operators can use the trader portal to interact with ICS2 through a user interface. Access depends on the applicable identity, authentication and authorisation arrangements.

Common investigation areas
  • UUM&DS registration and access rights
  • National authentication arrangements
  • Selected operator and delegated roles
  • Browser session and portal availability
  • Correct production or test environment
IDENTITY → AUTHORISATION → PORTAL
SYSTEM-TO-SYSTEM STI

Shared Trader Interface

Automated message exchange

A technical sender connects through an appropriately configured system-to-system solution, using the required communication and security mechanisms. An IT service provider may operate this connection.

Common investigation areas
  • AS4 access point and message exchange
  • Mutual TLS connectivity and certificates
  • Message sealing and sender identification
  • Endpoint and environment configuration
  • Technical receipts and response handling
SENDER → AS4 → STI
STP ACCESS DIAGNOSTICS

Login successful does not always mean access authorised.

Authentication establishes the user’s identity. Authorisation determines whether the user can perform the intended operation for the relevant economic operator.

01

Authentication failure

The user cannot complete the applicable sign-in procedure or identity verification.

Check

National login method, account status, authentication response and correct portal entry point.

02

Missing authorisation

The user signs in but cannot access the required ICS2 function or act for the intended operator.

Check

UUM&DS roles, permissions, delegations and the applicable EORI relationship.

03

Portal session problem

The interface fails to load, a session expires or a browser action does not complete.

Check

Session validity, browser compatibility, local network restrictions and published service notices.

04

Incorrect environment

The operator uses the wrong access route or expects production data in a test environment.

Check

Environment-specific URLs, permissions, registrations and configuration.

STI / SYSTEM-TO-SYSTEM

Follow the message. Across the connection.

For an AS4-based connection, the investigation should distinguish the transport layer, message security, sender configuration and subsequent business processing.

A successful network exchange does not, by itself, prove that the ENS has been registered.

Certificate distinction

Transport-layer TLS certificates and message-level sealing certificates serve different purposes. Check the certificate type, validity, trust, private-key availability and registration required by the applicable ICS2 specifications.

AS4 CONNECTION ANALYSIS REFERENCE MODEL
LAYER 01
Network & TLS

DNS, routing, endpoint reachability and mutual TLS negotiation

LAYER 02
AS4 message exchange

Access-point configuration, headers, message security and receipts

LAYER 03
ICS2 business validation

Message structure, data content and applicable business rules

LAYER 04
Filing status & notifications

Registration outcome, subsequent messages and recipient routing

VERIFY EACH LAYER INDEPENDENTLY
CONNECTIVITY TROUBLESHOOTING MATRIX

What the technical symptom may indicate.

The examples below describe possible causes, not definitive interpretations of a particular ICS2 error code.

Symptom Potential cause Diagnostic action Important caution
TLS handshake failure Certificate, trust-chain or mutual-authentication issue Inspect TLS logs, certificate validity and configured trust material. Do not disable certificate verification as a workaround.
Connection timeout Network interruption, endpoint issue or unavailable service Check connection logs, timing, routing and any service notices. Timeout does not prove that the original message was rejected.
AS4 processing error Messaging configuration, security or protocol mismatch Review the actual AS4 error and relevant interface specifications. Do not modify ENS business data without evidence of a data problem.
Certificate-related rejection Expired, incorrect or improperly registered certificate Check certificate purpose, registration, sender identity and environment. Transport and sealing certificates are not interchangeable.
Receipt exists; business response missing Response processing, routing or asynchronous delivery issue Correlate transport evidence with the business-message lifecycle. An AS4 receipt is not confirmation of ENS registration.
Test connection works; production fails Environment-specific endpoint, rights or configuration Compare production configuration with the approved deployment setup. Successful conformance testing does not prove current production connectivity.
PRACTICAL EXAMPLE / AS4

The connection times out. Was the ENS received?

A sender transmits an ENS message through its AS4 access point. The application reports a timeout before a definitive processing outcome is available.

The sender cannot safely conclude that the filing failed. The message may not have reached the receiving system, or the communication may have been interrupted after delivery.

Correct operational principle

Reconcile the original message identifiers, available receipts, technical logs and business notifications before deciding whether a retry or another recovery action is appropriate.

01
Message sent

Original transmission initiated

02
Timeout reported

Processing outcome not established

03
Evidence reconciled

Logs, receipts and filing references checked

04
Recovery decision

Action selected according to confirmed status

NO BLIND RESUBMISSION
SERVICE AVAILABILITY & BUSINESS CONTINUITY

A local outage is not an authorised contingency procedure.

If ICS2 appears unavailable, check official service communications and contact the appropriate support channel. Do not assume that an individual connectivity problem automatically activates a business continuity arrangement or suspends ENS obligations.

Where an official contingency procedure applies, follow its published scope, activation conditions and instructions.

SUPPORT & ESCALATION

Escalate with evidence, not assumptions.

Where the issue cannot be resolved locally, involve the technical sender, IT service provider or the appropriate National Service Desk, depending on the failure and the operator’s setup.

01 Identify the environment

Production or conformance testing, access channel and relevant configuration.

02 Provide message references

Technical message ID, relevant filing references and precise timestamps.

03 Attach diagnostic evidence

Relevant error responses, sanitised logs and the observed failure sequence.

04 Explain operational urgency

Affected filing, transport deadline and any outstanding customs instruction.

OFFICIAL TECHNICAL GUIDANCE

Consult the latest ICS2 specifications, operational FAQ and instructions issued by the relevant national customs administration.

03 / MESSAGE VALIDATION

Message rejected? Find the rule that failed.

A rejected ICS2 filing requires more than correcting an XML document. The problem may concern message structure, mandatory ENS particulars, business-rule consistency, operator identifiers or the status of an existing filing.

The effective error details must be taken from the received notification and the applicable ICS2 technical specifications. The examples below are diagnostic illustrations, not official error-code definitions.

01 / TECHNICAL STRUCTURE

XML & schema errors

The submitted message does not comply with the applicable technical structure or data format.

Typical checks
  • Correct message type and schema version
  • Element structure and cardinality
  • Permitted data types and field lengths
  • Namespace and technical formatting
VERIFY MESSAGE SPECIFICATION
02 / BUSINESS CONTENT

ENS data errors

The message is technically structured but fails one or more applicable data requirements or business validations.

Typical checks
  • Required particulars for the filing type
  • Valid codes and reference values
  • Consistency of goods and transport data
  • Conditional requirements and dependencies
VERIFY DATA REQUIREMENTS
03 / REFERENCES

Identity & linking errors

Identifiers or references may be missing, inconsistent or unsuitable for the intended filing operation.

Typical checks
  • EORI and relevant party identification
  • LRN and other applicable references
  • Master and house filing relationships
  • Sender role and filing responsibility
VERIFY REFERENCE CONSISTENCY
04 / FILING LIFECYCLE

Operation & status errors

The requested action may be incompatible with the declaration’s existing state or the applicable filing procedure.

Typical checks
  • Original filing versus amendment
  • Duplicate or previously processed requests
  • Permitted operation for the current status
  • Correct declaration and message references
VERIFY FILING LIFECYCLE
ERROR INTERPRETATION

Read the full response. Not just the notification code.

The notification identifies the type of system response. The diagnostic details explain what failed and where the correction should be made.

Always inspect the available error description, rule identifier, element reference and related message identifiers. Their exact format depends on the applicable message specification.

Do not confuse two separate questions

Was the message rejected? This is a processing-outcome question.

Why was it rejected? This requires interpreting the actual validation details.

VALIDATION ANALYSIS ILLUSTRATIVE DATA
MESSAGE TYPE ENS filing
PROCESSING RESULT REJECTED
ERROR CATEGORY Business validation
// CONCEPTUAL ERROR EXAMPLE

Field: Transport reference

Issue: Required value not supplied

Action: Check applicable data rules

Correct the source data

Validate the updated message before submitting the appropriate operation.

EXAMPLE ONLY — NOT AN ACTUAL ICS2 MESSAGE
CORRECTION WORKFLOW

From rejection to verified processing.

Treat the rejected submission as a traceable incident. Correct the underlying data or operation, then verify the actual system result.

01

Capture the rejection

Preserve the original message, response, timestamps and relevant filing references. Record every reported validation error.

02

Identify the failed rule

Determine whether the problem is technical, business-related, reference-related or connected to the requested operation.

03

Correct the authoritative data

Fix the source system or declaration data. Avoid altering an XML output manually while leaving the underlying defect unresolved.

04

Run local validation

Recheck the schema, applicable business rules, mandatory particulars and consistency of related references.

05

Submit the appropriate operation

Use the correct filing or correction procedure for the confirmed status. Do not assume that every rejection should be handled as an amendment.

06

Verify and close

Confirm the actual response, record the resulting references and investigate any remaining ENS completeness or risk-assessment requirements.

COMMON TROUBLESHOOTING MISTAKES

Corrections that create another problem.

01
Resending the same invalid payload

Repeated submission does not resolve an unchanged schema or business-rule defect.

02
Changing identifiers without checking the lifecycle

An arbitrary reference change can interfere with traceability or the relationship between related filings.

03
Using amendment procedures for the wrong status

A filing that was never registered must not automatically be treated as an accepted declaration requiring amendment.

04
Assuming registration means ENS completion

In multiple filing, other required submissions may still be outstanding after one filing has been registered.

05
Ignoring the original notification

A generic application message may hide detailed validation information supplied by the receiving system.

06
Confusing local checks with customs acceptance

Passing an internal XML validator does not establish that ICS2 will accept or register the filing.

SPECIAL CASE / MULTIPLE FILING

One filing accepted. ENS still incomplete.

When several parties contribute ENS data, a successful response for one filing does not establish that all required particulars have been provided.

Check the status of each expected filing, the relevant master and house references, and whether the submissions can be associated correctly.

Understand ICS2 Multiple Filing
ILLUSTRATIVE FILING RELATIONSHIP
MASTER-LEVEL FILING Registered Individual filing processed
EXPECTED HOUSE-LEVEL DATA Outstanding Completion not established
ENS COMPLETENESS Requires verification
04 / MESSAGE RECONCILIATION

Message sent. Outcome unknown.

An ENS message can leave the sender’s system without an immediately visible filing result. The problem may concern transport acknowledgements, asynchronous processing, notification delivery or the local application’s ability to correlate responses.

The correct recovery action depends on what can actually be confirmed. A successful transport exchange is not proof of ENS registration, and a missing local response is not proof of rejection.

END-TO-END MESSAGE TRACE

Follow the evidence across four boundaries.

CONCEPTUAL MODEL
01

Sender application

Original payload created and transmission initiated.

LOCAL MESSAGE ID / LRN
02

Transport exchange

Communication-layer delivery and available technical receipts.

AS4 / TRANSPORT EVIDENCE
03

ICS2 processing

Applicable validation and filing lifecycle operations.

BUSINESS PROCESSING RESULT
04

Response delivery

Business notification delivered and matched to the original request.

RECEIVED / CORRELATED / RECORDED

Critical distinction: transport evidence, business validation, ENS registration and completion of risk assessment are separate concepts. Do not substitute one confirmation for another.

MRN NOT RECEIVED

No MRN visible? Check what was confirmed.

A Movement Reference Number is associated with the relevant registered declaration or filing. Its absence from the sender’s application requires investigation, but does not by itself establish that ICS2 rejected the submission.

First determine whether the expected registration response was generated, whether it reached the technical recipient and whether the local application processed it correctly.

Do not invent or replace the MRN.

Keep the original LRN and technical message identifiers available for correlation. Record an MRN only when it has been assigned and confirmed by the relevant system response.

FILING STATUS INVESTIGATION EXAMPLE
Original message Sent
Transport receipt Available
Business response Not located
MRN Not confirmed
CONFIRMED CONCLUSION

Processing outcome unresolved

Locate or reconcile the business response before choosing a recovery operation.

Illustrative status display — not connected to ICS2
NOTIFICATION TROUBLESHOOTING

Six symptoms. Six different investigations.

Missing notifications can result from different causes. The evidence should identify whether the issue is in customs processing, technical delivery, recipient configuration or local software.

Observed problem What to verify Next diagnostic action
AS4 receipt received, no business notification Whether a business response was produced and delivered Correlate transport IDs with the business-message exchange and check response processing.
MRN absent from the local system Registration result and message import into the application Check the expected response, its recipient and any failed local parsing or mapping.
Notification received by another party Applicable notification recipient and filing arrangement Verify operator roles, technical sender setup and authorised message routing.
Response exists but is not linked to the filing Correlation references and local message-matching logic Compare original identifiers with those contained in the received response.
ENS remains incomplete after a successful filing Other required filings and master/house relationships Reconcile expected contributions and verify their registration and linking references.
Notification arrives later than expected Asynchronous processing, message queues and service availability Review timestamps and available status evidence before initiating another operation.
MESSAGE CORRELATION

Connect every response to its original submission.

Message reconciliation requires consistent identifiers, timestamps and a complete audit trail. Do not confuse a transport identifier with a customs filing reference.

01 / LOCAL REFERENCE

LRN

Identify the original filing using the applicable local reference and the sender’s own filing records.

02 / TECHNICAL EXCHANGE

Message ID

Trace the individual technical exchange using its message identifiers and available delivery evidence.

03 / CUSTOMS REGISTRATION

MRN

Record the customs reference where it has actually been assigned through the relevant registration process.

04 / PROCESSING HISTORY

Timeline

Reconcile timestamps, responses, retries and any later filing operations in the correct sequence.

PRACTICAL TROUBLESHOOTING SCENARIO

The message was delivered. The application shows nothing.

An operator submits an ENS through an STI connection. A technical receipt is available, but the local application displays no registration result.

Investigation reveals that a business response was received by the integration component but was not associated with the original filing.

In this illustrative scenario, the correct response is to repair the local correlation process and restore the filing status, not automatically create another original ENS.

01
Transport delivery confirmed

Technical receipt located

KNOWN
02
Business response located

Message found in integration logs

KNOWN
03
Correlation failure identified

Response not matched to the local filing

CAUSE
04
Local record reconciled

Actual filing outcome verified and recorded

ACTION
VERIFY FIRST — DO NOT CREATE A DUPLICATE
SAFE RECOVERY PROCEDURE

Resolve uncertainty without losing traceability.

01

Freeze uncontrolled retries. Preserve the original submission and establish which actions have already occurred.

02

Collect all available evidence. Review message identifiers, LRN, receipts, timestamps, application logs and received notifications.

03

Reconcile the processing result. Determine whether the original filing was rejected, registered or remains unresolved.

04

Check subsequent obligations. A registered filing may still require supplementary ENS data or a response to customs instructions.

05

Escalate unresolved cases. Contact the appropriate technical provider or customs support channel with the relevant evidence.

06

Document the final state. Record the confirmed result, corrective action and any remaining operational requirements.

05 / OPERATIONAL REFERENCE

ICS2 troubleshooting. Questions that matter.

Technical failures, rejected filings and customs notifications require different responses. These answers help economic operators distinguish confirmed processing results from unresolved system or operational problems.

FREQUENTLY ASKED QUESTIONS

Find the cause. Choose the right action.

Use the actual ICS2 response, the applicable technical specifications and the current instructions of the competent customs authority when resolving a specific incident.

ACCESS & CONNECTIVITY ENS VALIDATION MRN & NOTIFICATIONS MULTIPLE FILING CUSTOMS REFERRALS
01 Why is my ICS2 ENS message rejected?

An ENS filing may be rejected because it fails technical validation, applicable business rules, data requirements or checks associated with the requested filing operation.

Review the complete rejection notification, identify the reported validation errors and correct the underlying cause before submitting the appropriate message again.

02 What should I do if ICS2 does not respond?

First determine whether the problem concerns connectivity, message delivery, asynchronous business processing or notification handling.

Check the original message identifiers, transport evidence, application logs and available business responses. Do not assume that a timeout means the filing was rejected. Avoid uncontrolled resubmission while the original outcome remains uncertain.

03 Why have I not received an MRN?

The expected registration response may not have been generated, delivered, received or correctly processed by the local application. The absence of an MRN from your software does not independently establish rejection.

Reconcile the LRN, relevant technical message identifiers and available responses. Record the MRN only when its assignment has been confirmed.

04 Does an AS4 receipt confirm that ICS2 accepted the ENS?

No. A transport-level receipt concerns the technical message exchange. It must not be treated as confirmation that the ENS has passed business validation or been registered.

Check the relevant ICS2 business notification to establish the actual filing result.

05 Can an ENS be registered but still incomplete?

Yes. Under multiple filing arrangements, the registration of an individual filing does not necessarily establish that all required ENS particulars have been supplied.

Check the expected contributions, the master and house filing relationships, and the applicable completeness notifications.

Read the Multiple Filing guide
06 What is the difference between an ENS rejection and an amendment?

Rejection means the relevant submission has not been successfully registered through that processing operation. An amendment concerns changes to an existing registered ENS, subject to the applicable legal and system conditions.

Before choosing an operation, establish the actual filing status. A rejected original submission should not automatically be handled as an amendment.

07 What should I check when an ICS2 certificate fails?

Check the certificate’s purpose, validity, trust chain, private-key availability and registration or configuration requirements. Verify that the correct certificate is used for the relevant environment.

Transport-layer authentication and message-level sealing are distinct security functions. Do not disable certificate verification to bypass a connection failure.

08 Can I resend an ENS after a connection timeout?

Not without checking the original transmission outcome and the applicable recovery procedure.

A timeout may occur before or after message delivery. Reconcile the available technical and business evidence before deciding whether a retry is appropriate. This reduces the risk of duplicate or inconsistent submissions.

09 What happens if customs issues an RFI, RFS or Do Not Load instruction?

Customs referrals require action according to the specific instruction received. A request for information, a request for screening and a Do Not Load instruction are not interchangeable.

In particular, a Do Not Load instruction must be respected. Correcting or supplementing ENS data does not, by itself, authorise loading contrary to that instruction.

Explore ICS2 Incidents
10 Who should investigate a missing house-level filing?

The parties responsible for the relevant ENS data should verify their own filing obligations and the references needed to associate related submissions.

Depending on the filing arrangement, this may involve the carrier, freight forwarder, house-level filer and technical service provider. The investigation should identify the outstanding contribution, rather than assuming every participant must resubmit its data.

Understand House-level Filing
11 Does an ICS2 outage suspend ENS obligations?

A local connection problem does not automatically suspend the applicable ENS obligations or activate an official business continuity procedure.

Check service communications and the instructions issued by the competent customs authority. Use contingency arrangements only where their activation conditions and scope apply.

12 What information should I provide to ICS2 technical support?

Provide the affected environment, access channel, operator and technical sender identification, relevant filing references, message IDs, precise timestamps and the actual error or notification received.

Include sanitised diagnostic logs and explain any operational urgency. Do not disclose passwords, private keys or unnecessary personal or commercially sensitive information.

INCIDENT ESCALATION CHECKLIST

Before contacting support. Build the evidence file.

A complete incident record helps technical teams identify the failing component and reduces unnecessary exchanges between the economic operator, software provider and customs support.

Never include credentials or private keys.

Share only the diagnostic information required for the investigation, through the appropriate authorised support channel.

INCIDENT EVIDENCE PACKAGE 8 CHECKS
  • 01 Production or test environment identified
  • 02 STP or STI connection method recorded
  • 03 Relevant EORI and sender role identified
  • 04 LRN, MRN if assigned, and message IDs collected
  • 05 Exact timestamps and time zone recorded
  • 06 Actual error or business notification preserved
  • 07 Technical logs reviewed and sanitised
  • 08 Operational impact and urgency documented
COMPLETE EVIDENCE → TARGETED ESCALATION
PREVENTING RECURRING INCIDENTS

Turn troubleshooting into process improvement.

Repeated ICS2 errors often indicate a weakness in source data, software integration, message monitoring or the allocation of filing responsibilities.

01

Validate data upstream

Check required ENS particulars and reference consistency before message generation. Correct the original source of recurring errors.

02

Monitor every message state

Track submission, transport evidence, business responses and subsequent notifications without treating them as equivalent statuses.

03

Define ownership

Establish who investigates technical failures, missing house-level contributions, rejected filings and customs referrals.

04

Review recurring failures

Record incident categories, root causes, corrective actions and repeated defects. Use the findings to improve procedures and integration controls.

THE ICS2 TROUBLESHOOTING PRINCIPLE

Identify the failing layer. Confirm the actual filing status. Resolve the cause without losing traceability.