OneLake event trigger not firing in Dev workspace but works in QA and UAT

Question

We are facing an issue with OneLake event triggers in Microsoft Fabric and are looking for guidance.

Environment setup:

• Three Fabric workspaces: Dev, QA, UAT

Each workspace has its own Lakehouse and pipelines

Master pipelines run in UAT on a schedule

Master pipelines:

Ingest files from an FTP source

  Write files to the **UAT Lakehouse**

  
     Copy the same files to **QA and Dev Lakehouses**
```**Trigger configuration:**

Each workspace has **child pipelines**

Child pipelines use **OneLake event triggers**

Triggers fire on file creation in specific Lakehouse folders

Trigger configuration is identical across Dev, QA, and UAT

**Issue:**

OneLake triggers fire successfully in **UAT and QA**

**Dev triggers do not fire**, even though:

   Files are created successfully in the Dev Lakehouse
   

Folder paths match the trigger configuration

Multiple retries performed and trigger settings validated

Any guidance or troubleshooting steps would be appreciated. I can share workspace IDs, pipeline names, screenshots, or logs if needed.We are facing an issue with **OneLake event triggers in Microsoft Fabric** and are looking for guidance.

**Environment setup:**

Three Fabric workspaces: **Dev, QA, UAT**

Each workspace has its own Lakehouse and pipelines

**Master pipelines** run in **UAT** on a schedule

Master pipelines:

   Ingest files from an FTP source
   

Write files to the UAT Lakehouse

 Copy the same files to **QA and Dev Lakehouses**

Each workspace has **child pipelines**

Child pipelines use **OneLake event triggers**

Triggers fire on file creation in specific Lakehouse folders

Trigger configuration is identical across Dev, QA, and UAT

**Issue:**

OneLake triggers fire successfully in **UAT and QA**

**Dev triggers do not fire**, even though:

   Files are created successfully in the Dev Lakehouse
   

Folder paths match the trigger configuration

Multiple retries performed and trigger settings validated

 Are there any **known limitations, workspace-level settings, permissions, or capacity-related constraints** that could cause OneLake triggers to fire in QA/UAT but not in Dev?  
 Are cross-workspace file copies or overwrite scenarios known to affect OneLake triggers?

Any guidance or troubleshooting steps would be appreciated. I can share workspace IDs, pipeline names, screenshots, or logs if needed.

Answer 1

hi there Mahima Rao Kolli and thx for yours question at Q&A,

In Microsoft Fabric, OneLake event triggers fire only on native write events that happen inside the same workspace. In your setup, Dev is not failing because of the path or trigger configuration, but because of how the files are written into the Lakehouse. You write the files to UAT first and then copy them to QA and Dev from another workspace. In UAT and QA the trigger fires because the write is treated as a real file creation event. In Dev, the copy operation is often handled as an overwrite or a service-side sync. For OneLake, that is not a real event. The file exists, but no event is emitted, so the trigger does not fire. This is really known behaviour. OneLake event triggers are not guaranteed when you use cross-workspace copy operations, overwrite existing files, or rely on service replication where no actual create event is raised.

The most reliable option is to write files directly into the Dev Lakehouse instead of copying them from UAT. If Dev is only used for debugging, add an explicit touch step in the pipeline: create a new file or a temporary marker first, then copy the data. Another option is to avoid event triggers in Dev altogether and run the child pipeline on a schedule or trigger it explicitly from UAT. I'm pretty sure, Dev is not broken. OneLake simply does not treat your operation as an event.
for sure if you want to be 100 % sure, try to run a simple test. In Dev, manually drop a brand new file into the same folder, either through the UI or via a small pipeline that writes directly to the Dev Lakehouse. If the trigger fires, the case is closed. The issue is the cross workspace copy.

If it does not fire even then, you would look at the Dev workspace capacity, the permissions of the managed identity on the Lakehouse, and whether the event trigger in Dev is actually enabled and not paused.

But in practice, in 9 cases out of 10 the root cause is the copy between workspaces. OneLake is not malfunctioning. It simply does not treat that operation as an event.

Have a good luck,

Alex