PegaVersion 82 - Reloadsection loads incorrect section


Recently moved from pega 721 to pega 82 version, in some screens system loads incorrect section.

I do see Reloadsection activity is updated in pega 82 version.

Anybody facing this issue, do we have any hot fix for it.


Keep up to date on this post and subscribe to comments

September 25, 2019 - 11:44pm

I tried to search for an existing issue in 8.2 version related to "ReloadSection" activity. It is an activity which is used widely.  If ReloadSection is having the issue, we would have received some tickets related to it.

October 4, 2019 - 12:06am
Response to Rachit_Agarwal

Thank you Rachit.

Let us know where I get list of pega 8.2 issue with corresponding hotfix , so that our team proactively install and monitor the pega 82 issues

September 26, 2019 - 7:48am

HI John,

How you are calling the relaod it is vai some activity or using the reload API in Javascript?

or if you can share the tracer for the working and non working scenario then we can  get more info on this to help you out.

September 27, 2019 - 12:11pm


It is possible you are running into some Page context issue and might not be a simple reload section issue. I suggest that you verify from the clipboard that the data on the clipboard page for the section in question is correct. Also, please verify from the Tracer the parameters passed to ReloadSection activity to debug further.

If you are refreshing the current section, look for the parameter StreamName.

For refresh other section, look for the parameter StreamList and see if there are multiple tokens of same section name are passed, this can be critical here when you debug.

Hope, this helps!

September 27, 2019 - 2:32pm


If you are using the reload section API , are you using the getSection API to get the section or directly hardcoding the section name?


October 4, 2019 - 12:15am

@sahuv1 @TANIE @mutha1

we are using refresh other section in the dropdown property action.

when i trace found two things 1. Reload section called twice  2. In First refresh it has correct StreamList, what is configured in refresh other section and In the second refresh it refers some other section in StreamList so it loads incorrect section in the screen.

one common thing between first refresh and second refresh section are referring same set of properties.