Document Retrieval Fails When One of Several File Name Patterns Matches Nothing
What does "evaluating expression: org.mvel.ExecutableAccessor@1a0a09b4" mean in Workday Core Connector?
The Document Retrieval step evaluates a file-name expression for each pattern you configured on it. If one of those patterns finds no matching file in the source folder, that expression cannot resolve and the whole retrieval fails, so any later patterns on the same retrieval never run. It looks intermittent because it only fires on the runs where a file happens to be missing.
Quick fix
Put a file matching every configured pattern into the source folder and re-launch, or temporarily remove the pattern that has no file so the remaining files can be retrieved.
Permanent fix
Configure one Document Retrieval per file pattern instead of several patterns on a single retrieval, so each one succeeds or fails independently and a missing optional file no longer blocks the files that are present. Where the source system writes into a folder used only by this integration, a single retrieval with one catch-all pattern is simpler still and avoids the situation entirely.
Troubleshooting
- Open the failed integration event and confirm the failure is in the Document Retrieval step, not in transformation or delivery.
- List every File Name Pattern configured on that single Document Retrieval. The error fires when any one of them matches no file.
- Look at the source folder as it was for the failed run and work out which patterns had a file and which did not.
- Compare against a run that succeeded. Successful runs normally had a file for every configured pattern, which is what makes the failure look random.
- Confirm it by retrying with only the pattern that had a matching file present. The expression error should not appear.