Why does my shipment not become visible upon an update of Scope?

After an update or restart of the Scope Server, Scope may need to rebuild large indexes, which can temporarily delay the visibility of older shipments within the system.

When a Scope Server is started, it verifies whether any indexes need to be rebuilt. This situation may occur following a Scope Server update or if a prior index rebuild was not completed successfully. If necessary, the Scope Server will initiate an index-rebuild process specifically for specific tables. During this process, users can already log in and perform their tasks. However, any records that have not yet been indexed will not appear on the home screens for those shipments, even though they are present in the database.

This index-rebuild process prioritizes the indexing of the most recent shipments, specifically those from the last 30 days, ensuring they are visible to users as quickly as possible. A shipment may not yet be visible in the Air/Sea Import/Export shipment application, but it could already be accessible in the Shipment Overview. In such cases, you can easily locate and open the shipment from there.

There is no need to panic nor to contact our service desk. Our service desk cannot speed up the rebuild process. It may take up to 24 hours for the index to be fully rebuilt.

If in doubt, please check our status page.