You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I select a source for RC/DRC counts on the Configuration page and then search for a concept on the Search page, the RC/DRC/PC/DPC columns populate with the counts for that source database.
Actual behavior
Upon searching for a concept, all counts show as 0. The counts only show up after I refresh the page in my browser.
Steps to reproduce behavior
On the Configuration page, select a new source from which to pull the RC/DRC counts. Then, click on Search and search for something. All of the counts will show as 0. Then, refresh the page in your browser. The counts will now show up.
The text was updated successfully, but these errors were encountered:
This is the one pattern I've confirmed results in all 0's. However, it also randomly happens at other times. Refreshing the page always does the trick to have the counts show up again.
Also wanted to mention that sometimes, counts will populate but not the correct counts - fewer concepts with counts and lower counts overall show up. Then after refresh, all of the counts for the data source selected on the Configuration page will show.
@chrisknoll do you know if this might be an issue with our ATLAS instance, or a bug in the app? thanks.
Expected behavior
When I select a source for RC/DRC counts on the Configuration page and then search for a concept on the Search page, the RC/DRC/PC/DPC columns populate with the counts for that source database.
Actual behavior
Upon searching for a concept, all counts show as 0. The counts only show up after I refresh the page in my browser.
Steps to reproduce behavior
On the Configuration page, select a new source from which to pull the RC/DRC counts. Then, click on Search and search for something. All of the counts will show as 0. Then, refresh the page in your browser. The counts will now show up.
The text was updated successfully, but these errors were encountered: