Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Issue with Microsoft Fabric Task Flows Not Locating Artefacts in Subfolders

Hello everyone,

I'm facing an issue with our task management system where task flow links are unable to locate artefacts in subfolders, despite being properly attached. The artefact can only be accessed when I manually navigate to the specific subfolder.

  • Problem Description: Clicking a task flow link that should direct to an artefact within a subfolder results in the system failing to locate it.
  • Workaround: Currently, the only way to access the artefact is by manually navigating to the subfolder where it's located.

Has anyone encountered a similar issue? I would appreciate any suggestions on how to resolve this or any possible workarounds.

Thank you for your help!

8 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous ,

    Thanks for using Fabric Community.
    Inorder to understand your issue clearly, can you please share the screenshots of the activity you are trying to do.
    If you can provide these details, I would be able to help you with your issue.



    • Anonymous's avatar
      Anonymous
      Not applicable

      Hello Anonymous ,

      We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .
      In case if you have any resolution please do share that same with the community as it can be helpful to others .
      Otherwise, will respond back with the more details and we will try to help .
      Thanks

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi Anonymous ,

        We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .
        Incase if your query is similar to the below thread, then as said it looks like a bug.

        I hope this is helpful. Do let me know incase of further queries.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you for the update. I appreciate you bringing up this similar post that highlights it as a bug issue. Please keep us informed when the issue is resolved.