Dashboard freeze

Bug Report
1

Hey there,

Sometimes when my teammates and I are making changes on a dashboard, something happens and all the screen freezes.
Inspecting the page, we found this div overlaying all the page

image
image1435×977 76.3 KB

2

Hey @Thiago_Andrey_Zils,

Thank you for bringing this to our attention. It seems that there is an issue with one of the underlying libraries that we use. Our engineering team is taking a closer look now. I will be sure to follow up with you as soon as we release a fix for this.

Thank you,
Heath

3

Hey @Heath any updates on that ?

The problem is happening a lot, and that made me lost a lot of codes because i cant save my dashboards blocks.

For those whos having the same problem here’s a tip, use this code on the console of your browser:

document.getElementById('submit-save-dashboard-block').click();
4

@Thiago_Andrey_Zils,

I do not have any updates currently. Though, I am interested in the frequency you are seeing this occur. Do you have steps to reproduce this error? Could you walk me through those? Are you seeing the issue when working on specific blocks?

Thank you,
Heath

5

@Heath they usually happens on custom html blocks, but some of my team mates are noticing on editing workflows as well

6

That’s right, in recent days this has been happening frequently during workflow development

1 Like
7

+1. For me this happens when I click on the edge on the block where you change the size of that particular block, but not change it. Just a click is enough to freeze the dashboard. For me the only way to recover from this is to refresh the page.

This the class of the element I click on to freeze the whole page : react-resizable-handle react-resizable-handle-se
image

8

Thanks, that extra bit was helpful. We have identified a fix and should have it out in our next software release.

2 Likes
9

Hey Dylan, that issue is still happening :frowning:

Any update on that ?

10

We deployed a fix for this issue to our public cloud on May 10, 2022. Users who are on private installations would have gotten the fix once that version of Losant was deployed to their environments, which should be true for almost all of our customers by this point.

@Thiago_Andrey_Zils can you send a screen recording of the bug and steps to reproduce if they are different from the ones listed above? I want to verify that what you’re seeing is not a completely separate issue or that it’s reached through some other user action, as I am unable to reproduce it anymore.