Using fileExists on symlinks

I am having difficulty with using the fileExists tool in regards to symlink folders. The following if(fileExists("last_working")) refers to a folder in the current directory that are symlinked to a real folder. My Jenkins job is executed on a Linux machine, MacOS machine, and a Windows machine that is using the Cygwin terminal in a parallel workflow. I have verified that fileExists works for Linux and MacOS, but it is failing for my Windows/Cygwin job. Is this the intent of fileExists, or should it work for my Windows exector?

Jenkins setup:

Jenkins: 2.249.3
OS: Linux - 4.4.0-128-generic
Java: 1.8.0_242 - Oracle Corporation (OpenJDK 64-Bit Server VM)
---
ace-editor:1.1
ant:1.11
antisamy-markup-formatter:1.5
apache-httpcomponents-client-4-api:4.5.13-1.0
authentication-tokens:1.4
aws-credentials:1.29
aws-java-sdk:1.11.995
bouncycastle-api:2.20
branch-api:2.6.2
build-timeout:1.19.1
cloudbees-folder:6.14
command-launcher:1.5
copyartifact:1.45.3
credentials:2.3.18
credentials-binding:1.24
display-url-api:2.3.4
docker-commons:1.16
docker-workflow:1.25
durable-task:1.35
ec2:1.57
echarts-api:4.8.0-2
email-ext:2.80
git:4.4.5
git-client:3.5.1
git-server:1.9
github:1.32.0
github-api:1.117
github-branch-source:2.9.1
gradle:1.36
handlebars:1.1.1
hidden-parameter:0.0.4
jackson2-api:2.12.3
jdk-tool:1.4
jquery-detached:1.2.1
jquery3-api:3.5.1-1
jsch:0.1.55.2
junit:1.31
ldap:1.25
lockable-resources:2.10
mailer:1.32.1
mapdb-api:1.0.9.0
matrix-auth:2.6.2
matrix-project:1.18
momentjs:1.1.1
node-iterator-api:1.5.0
okhttp-api:3.14.9
pam-auth:1.6
parameter-separator:1.3
pipeline-build-step:2.13
pipeline-github-lib:1.0
pipeline-graph-analysis:1.10
pipeline-input-step:2.12
pipeline-milestone-step:1.3.1
pipeline-model-api:1.7.2
pipeline-model-declarative-agent:1.1.1
pipeline-model-definition:1.7.2
pipeline-model-extensions:1.7.2
pipeline-rest-api:2.19
pipeline-stage-step:2.5
pipeline-stage-tags-metadata:1.7.2
pipeline-stage-view:2.19
pipeline-utility-steps:2.8.0
plain-credentials:1.7
plugin-util-api:1.2.2
resource-disposer:0.14
saferestart:0.3
scm-api:2.6.4
script-security:1.75
snakeyaml-api:1.27.0
ssh-agent:1.22
ssh-credentials:1.18.1
ssh-slaves:1.31.2
structs:1.22
subversion:2.13.2
thinBackup:1.10
timestamper:1.11.6
token-macro:2.12
trilead-api:1.0.13
variant:1.4
windows-slaves:1.6
workflow-aggregator:2.6
workflow-api:2.40
workflow-basic-steps:2.21
workflow-cps:2.86
workflow-cps-global-lib:2.17
workflow-durable-task-step:2.35
workflow-job:2.40
workflow-multibranch:2.22
workflow-scm-step:2.11
workflow-step-api:2.23
workflow-support:3.6
ws-cleanup:0.38

Symbolic links are complicated enough that you should probably just make a call to a shell command to make that decision rather than using the fileExists convenience method. Symbolic links on Windows file systems are especially interesting.