---
title: "Scenarios - File tracking - Lasernet tracking - Lasernet FO Connector"
slug: "file-tracking-scenarios"
description: "Those listed on this page are example scenarios and their expected results. Read the File Tracking guide for more information on the File tracking feature."
updated: 2025-08-27T10:17:30Z
published: 2025-08-27T10:17:30Z
canonical: "kb.lasernetgroup.com/file-tracking-scenarios"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scenarios

The following are example scenarios and their expected results:

- The Lasernet server is turned off in **Lasernet** > **Setup** > **Administration** > **Lasernet servers**.

Expected result:

No pending file is available because the XML file has not been created, as there is no active Lasernet server.
- The Azure Service Bus connection string has been entered incorrectly.

Expected result:

The pending file is created when Lasernet FO Connector creates the XML file.

An end user selects the pending file from the **Pending files** list and clicks **Check status**.

The file moves from **Pending files** to **Missing files**.
- The Azure Storage connection has been incorrectly configured.

Expected result:

The pending file is created when Lasernet FO Connector creates the XML file.

The **Lasernet report file check** batch job has been set up to run once every minute.

The file moves from **Pending files** to **Missing files** once the batch job runs.