Forum Discussion

Element115's avatar
Element115
Memorable Member
2 years ago
Solved

BUG::UI issue during DFg2 refresh

STEPS:

 

0__publish a DFg2.

1__Wait until the automatic refresh starts.

2__Click on the ... menu and select Refresh history.

3__The refresh history window opens and you can see a spinning circle and the words 'In progress' while the refresh is not finished.

4__When the refresh actually completes successfully, the UI does not refresh and you are left there wondering why is the spinner still there?  

5__Hit F5 to refresh the page and now the UI shows 'Succeeded' as in the screenshot below.

 

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi Element115 , Joshrodgers123  -

    We have update from internal team -
    " This is expected for now soon you will get a refresh button within the refresh history UX to update the values in the screen without the need to close and re-open the refresh history. and later on you get a automatically updated screen "

    Hope this is helpful. Please let me know incase of further queries.

5 Replies

  • I see the same thing too. The refresh history page does not update unless your refresh the page or exit it and go back in.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Element115 , Joshrodgers123 

    Thanks for letting us know about this! While it may not be a bug right now, we will hear your feedback and appreciate you taking the time to share it.

    I request you please share the feedback on our feedback channel . Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your feedback against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

     

    Hope this helps. Please let me know if you have any further queries.

    • Joshrodgers123's avatar
      Joshrodgers123
      Advocate V

      Hi Anonymous - all other refresh indicators in Fabric update when the refresh completes without you needing to refresh the entire browser page. Why would this one work differently? This sounds like a bug, not an "idea".

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi Joshrodgers123 , Element115 -

        Apologies for this unexcepted behaviour.

        At this time, we are reaching out to the internal team to get some help on this. I will check with the team for the fix. We will update you once we hear back from them.

         

        Thank you.