8.1 Known issues

8.1.1 Redirected requests

OpenLCA currently does not support handling redirected requests (e.g. reverse proxy).

8.1.2 Fetching deleted data sets

Fetching deleted data sets that were not used in the local database of the user who commits but that are used in the local database of the user who fetches will lead to broken references e.g.

  1. User A deletes a flow that is not used in the user’s local database and commits the deletion to the LCA Collaboration Server
  2. User B added a new process in the user’s local database and uses the flow as input
  3. When User B then fetches the changes of User A, the flow is deleted locally, but the input in the process still refers to the (now) deleted flow

Workaround: If a user is aware that another user is going to fetch a deletion of a (locally) linked element, modify any field in the element in question (e.g. add a letter in the name and remove it again and save). OpenLCA will track that the model has changed. When fetching the ”deletion” a conflict will come up and the user can manually choose to keep the local element.