You’re hitting a validation error coming from Amazon Bedrock because of how the Agent’s output schema is defined.

From the log:

“The 'integer' type in the 'output_config.format.schema' keyword does not support the 'maximum' and 'minimum' properties.”

So, somewhere in the Agent definition, an output field with type integer has minimum/maximum constraints configured. Bedrock doesn’t accept those constraints for integer fields in the schema, so the call fails before the model even runs.

Where to fix it in OutSystems

1. Open the Agent in Service Studio

   • In your O11 dev environment, open the module where you cloned the Agent (CloneOfStarDeliveryAIAgentApp or the producer that contains CloneOfStarDeliveryAIAgent).
   • In the left tree, find Logic > AI Agents > CloneOfStarDeliveryAIAgent (or similar name).

2. Edit the Agent’s Output Format / Schema

   • Select the Agent.
   • In the Properties pane, look for something like:
     • Output Format / Output Schema / Response Schema
       (exact naming depends on the Agent template you used).
   • There you’ll see a JSON schema or a list of fields. One or more fields will have:
     • "type": "integer"
     • and also "minimum": ... or "maximum": ...

3. Remove unsupported constraints You have three options:

   • Option A – Remove minimum and maximum (simplest)

     • For all integer fields in the output schema, delete the minimum and maximum properties.
     • Keep only type: "integer" (and other supported attributes such as description).

   • Option B – Change type to number

     • If you really need minimum / maximum, you can:
       • Change type from "integer" to "number" and keep minimum and maximum.
     • This keeps the validation while using a supported numeric type.

   • Option C – Change to string and validate in logic

     • If you prefer to avoid model-side validation, make the field string in the schema and do your own validation in OutSystems logic after the response.

4. Publish and test again

   • Publish the module with the corrected schema.
   • Go back to the “Test your Agent” screen (the one with PlayerEmail and PlayerGUID).
   • Click Test again and confirm the error disappears.

Why the data type mismatch shows up now

This is not a mismatch between PlayerEmail / GUID and your entities – it’s the Agent’s Bedrock configuration rejecting the output schema before execution. As soon as Bedrock sees integer + minimum/maximum, it responds with BadRequest, which is what you see in the error log.

Once you remove or adjust those constraints in the Agent’s output schema and republish, the Agent should run without this OS‑BERT‑62000 / OS‑ABRS‑FM‑40001 error.

If you can’t find the exact schema block, check all places where the Agent defines its “Expected Output” / “Structured Output” / “JSON Fields”; the problematic field will be one of the integer ones used there.