Long lasting update on last page of PURs

Steps to reproduce this issue:
this only works with 30+ PURs

  • select ‘Issues’ on left side
  • select PUR
  • start clicking ‘>’ to get next page(s)
  • when reaching last page it takes 15s to update the list

can’t upload video. use this LINK (something went wrong): https://cloud.indea.si/index.php/s/nAYTjtysgGsGfbe

WME Beta Permalink:
n/a
This bug occurs in:
ROW
WME Beta version number:
current one, none displayed
Are you using scripts? which ones?:
same with or without scripts enabled

1 Like

Here managed to upload video.
(reported ‘Something went wrong’ on the bug report form.

1 Like

Hi @gorankav,

Thank you for your report. I have filed an internal ticket to look into this issue and will keep you posted on the updates.

All the best,
Olesya

1 Like

Hello @gorankav,

There have been some performance improvements to the issue tracker. Could you please let me know if they have taken effect on your end?
Regarding the loading of results: The system is designed to load results in batches. While navigating through the initial 500 results should be rather smooth, fetching the next set (the next 500 results) might take a few seconds – typically no more than 15 seconds.

I will be awaiting your verification.

All the best,
Olesya

1 Like

wrong message. can’t delete it

1 Like

message in wrong topic. can’t delete it

1 Like

I’ve made some tests.
Initially it shows 483+ PURs, up to section 451-480 it switches quickly (obviously loaded in browser).
Going over to 480-501 it takes about 45-55s to refresh
Noted that production WME takes roughly 10% more time. (this might be a coincidence)
After the refresh it shows 983+ PURs.

BTW: why it does not show 500+? Where have you got this x83 (17 less than the block size)?

1 Like

Hi @gorankav,

Thank you for your response and sorry for the delay on my part.

Do you use the managed area filter by chance?
There is only a known performance issue with the managed area filter, when map suggestions are included in the issue tracker search.

Best regards,
Olesya

1 Like

Hello @gorankav,

As announced in today’s release post, this issue should now be fixed. I’d appreciate it if you could check this on your end.

Best regards,
Olesya

1 Like

Hi @Olesya-Staff ,

Now it works like a charm, in beta & prod.

Nice work

1 Like