If you are accessing files through symbolic links and have execution sandboxing enabled, the link target must be mapped into the container and must be at the same location within the container as it is on the host system. This can be done by configuring the correct data connections through the data repository, and on Windows ensuring that the container mappings are configured correctly for the source of the link. The target of the link must be the same on both host and target and therefore should not require specific mappings.
For example, the location Q:/myLocation/ is a symbolic link pointing at: C:/symbolicLinkTarget.
For this to work, Q:/myLocation/ must be mapped into the container. This could be mapped as, for example: C:/someLinkSource. The target of the link C:/symbolicLinkTarget must be mapped into the container and available within the container as C:/symbolicLinkTarget.
If C:/symbolicLinkTarget was not mapped into the container, the symbolic link and therefore the resolution of files within Q:/myLocation/ would not work within the container.
Further, if Q:/myLocation/ pointed at a target location which was not on the C:/ drive then the links would never be able to work on Windows within an execution container because it is only possible to mount into C:/ locations on Windows.