# Valid terminal credentials shown as invalid and terminal data stopped

**URL:** <https://community.dockflow.com/t/valid-terminal-credentials-shown-as-invalid-and-terminal-data-stopped/86>\
**Category:** Known and fixed issues\
**Created:** [November 6, 2026, 2:44pm UTC](https://community.dockflow.com/t/valid-terminal-credentials-shown-as-invalid-and-terminal-data-stopped/86 "2026-11-06T14:44:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [November 6, 2026, 2:44pm UTC](https://community.dockflow.com/t/valid-terminal-credentials-shown-as-invalid-and-terminal-data-stopped/86/1 "2026-11-06T14:44:43Z")

</div>

**Status:** Fixed since May 2026

**How to recognise it**  
In the Data Integrations console, you saw valid PSA Antwerp e-portal credentials reported as invalid. You could not save or validate new terminal credentials. The credential test did nothing, and terminal data for the shipment stopped coming in.

**Which shipments this affects**  
Shipments that rely on terminal data from the PSA Antwerp e-portal connection.

**What changed**  
Dockflow now recognises terminal credentials as valid when the sign-in succeeds. The credential test now shows whether the credentials are valid. You can save and validate PSA Antwerp e-portal credentials in the Data Integrations console, and terminal data for the shipment can come in again.

**Is past data corrected?**  
Nothing to correct: the change affects how new data is read.

**How to check your shipment**  
Open Data Integrations, select the PSA Antwerp e-portal connection, and run the credential test. A valid credential should pass. Then open a shipment that uses that terminal and check that terminal data is present. Contact support if the test fails or the shipment still has no terminal data.

**Do you need to do anything?**  
Nothing.