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
I believe it's a race condition. There are two responses sending a set-cookie header for the Authorization cookie (project service and import service). So, the import request is made for one user id, and the request for the newly created analysis is made for another user id.
I'm guessing these requests are made in parallel. A possible fix is to make them serial, but I think this can be a challenge. Another option is to add some blocking logic when the Authorization cookie is not yet set.
We need to add some more control-flow logic related to bearer tokens to handle expiration, so this can probably fall into that task. I will link the issue to this one (I may need to create it, first).
It turns out I misread the network requests. The two responses that set the Authorization cookie are the project endpoint and the count-page-view metrics endpoint.
E.g. make a new private window and try to import an analysis
https://qa.clinepidb.org/ce.b34/app/workspace/analyses/msRhETv/import
After clicking "agree" - reloading the page goes fine.
The text was updated successfully, but these errors were encountered: