I think this approach with repl- unnecessary rises the complexity...

It becomes harder to follow when repl- should be used in the code and when it shouldn't (you don't use it in reloadReplAgmts and reloadReplWinsyncAgmts, for example).

IMO, it'll be better to store all of the suffix data in one state as we do now.

And then we can check if we need to load the database data for suffixes or not:

src/cockpit/389-console/src/monitor.jsx
@@ -352,7 +352,11 @@ 
              };
          });
      } else {
-             if (selectedNode.id in this.state) {
+             if (
+                 selectedNode.id in this.state &&
+                 ("chainingData" in this.state[selectedNode.id] ||
+                     "suffixData" in this.state[selectedNode.id])
+             ) {
                  // This suffix is already cached
                  this.setState(prevState => {
                      return {

Or maybe you can add more comments in the code...

@spichugi - changes made please review...

LGTM!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3837

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.