Output URLs are sometimes files that do not exist

[Josh-XT]

Description

Output URLs are sometimes files that do not exist. The model is not referencing the correct file from its workspace. We need to check if the file it is referencing exists prior to sending the response and update and incorrect links with the most similar file in the agent's conversation workspace.

For example, with the 3D Modeling extension, the LLM gave the wrong link in the final response even with the correct link in context.

Here is a screenshot:

With the correct link /outputs/dd53f240-27aa-4213-87e2-5fc3847a9e3c/3af34fa0-91f3-4903-b742-548a9694467e//model_20250214_131224.stl.

The final chat message uses a broken link: /outputs/dd53f240-27aa-4213-87e2-5fc3847a9e3c/3af34fa0-91f3-4903-b742-548a9694467e/cube_20x20x20.stl and that triggers a 500 internal server error instead of 404 not found when it's opened.

So two issues:

• The chain produces bad output (invalid link).
• The file serving system makes an unhandled exception if the file isn't found.