Forum Discussion

BEJCC's avatar
BEJCC
Frequent Visitor
1 year ago
Solved

Copy Job Artifacts showing in OneLake File Explorer For Windows

After reaching GA, I've started implementing Copy Jobs into my Fabric Engineering Workspaces.
Looking online, I haven't found a report for this issue, if it is an actual issue.

When using the Onelake File Explorer for Windows, Copy Job artifacts show up in the explorer next to my Lake- & Warehouses.
Opening the artifact however, shows no contents.
Isn't a copy job compute only? Why do these objects appear in the explorer? Is this intentional?

Thank you!

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi BEJCC ,

    Thank you for reaching out to the Microsoft Fabric Community.

     

    The behavior you are observing, Copy Job artifacts appearing in OneLake File Explorer without containing data is intentional and consistent with Microsoft’s design for Microsoft Fabric.

    These artifacts are metadata objects that represent the execution of Copy Jobs within the system. Although they do not store actual data, they are essential for tracking and monitoring the execution status of the jobs. This design ensures that the system retains visibility and control over data movement tasks, even when the jobs themselves do not generate persistent data files.

    For additional details, you may refer to the official Microsoft documentation on the Copy Jobs in Microsoft Fabric.

     

    If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

     

    Thankyou.

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi BEJCC ,

    Thank you for reaching out to the Microsoft Fabric Community.

     

    The behavior you are observing, Copy Job artifacts appearing in OneLake File Explorer without containing data is intentional and consistent with Microsoft’s design for Microsoft Fabric.

    These artifacts are metadata objects that represent the execution of Copy Jobs within the system. Although they do not store actual data, they are essential for tracking and monitoring the execution status of the jobs. This design ensures that the system retains visibility and control over data movement tasks, even when the jobs themselves do not generate persistent data files.

    For additional details, you may refer to the official Microsoft documentation on the Copy Jobs in Microsoft Fabric.

     

    If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

     

    Thankyou.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi BEJCC ,

      I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.


      Thank you.

  • Hi BEJCC It might be because of workspace metadata synchronization, which causes Copy Job artifacts to appear in the OneLake File Explorer even though they are compute-only.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi @BEJCC ,

    I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.


    Thank you.