Optimization Quest Runs Successfully but Endpoint Execution Fails

DivyaGorrela

Hi everyone,

I'm working on an Infor AI Optimization model. The Quest runs successfully and returns an optimal solution (CBC solver, objective value generated correctly).

However, when I create and activate an Endpoint from the same Quest, the Test Endpoint fails with:

"Error occurred while executing the endpoint"

I have already:

• Verified the Quest runs successfully
• Deleted and recreated the Endpoint multiple times
• Activated the Endpoint
• Checked History Logs (only shows "Create", no execution details)

Has anyone experienced an Optimization Quest working correctly but the Endpoint failing with this generic error? Is there a way to view a detailed endpoint error log?

Endpoint Error.jpg

Thanks in advance.

Mary Green

Hi @DivyaGorrela Here is what our team member had to say:

When I deployed the Employee Name matching Quest on a tenant.

This was some of things, I hit.

1. Input schema didn't match the trained schema exactly (column names case-sensitive; numerics-as-strings vs true numerics)
2. Model was retrained but the endpoint deployment wasn't republished — endpoint stays "Active" but points at a stale artifact
3. Tenant/logical-ID context missing on the call (we had to add x-infor-logicalidprefix: lid://infor.colemanddp)

Looking at the screenshot — the JSON values are all quoted strings ("SPACE_LIMIT": "50", "POTENTIAL_REVENUE": "10", "COST": "23"). Coleman Optimization Quests typically expect numeric types for numeric features. If the Quest was trained on numerics and the test payload sends strings, the solver explodes inside the wrapper and you get exactly this generic error. That's the first thing I'd change — drop the quotes around the numeric values.

Other things worth checking on Divya's endpoint:

• Re-run the Quest in the Quest Modeler UI with the same inputs — if it solves clean there, the model is fine and the deployed endpoint is the problem (redeploy)
• Check the History Logs tab right there in the screenshot — sometimes it shows the underlying error (solver infeasible, schema mismatch, IDP timeout) the modal hides
• Confirm the endpoint actually has artifacts bound — Coleman has a known gotcha where "Active" status doesn't guarantee a successful deployment