Skip to content

Conversation

@ctiliescuuipath
Copy link
Contributor

@ctiliescuuipath ctiliescuuipath commented Dec 15, 2025

  1. change func behavior for deterministic guardrails. If func == true return validation error
  2. update name of the func to something more meaningful

1. change func behavior for deterministic guardrails. If funct == true return validation error
2. update name of the func to something more meaningful
@ctiliescuuipath ctiliescuuipath force-pushed the AL-229-integrate_deterministic_guardrails branch from ee2a138 to 4aafd2c Compare December 15, 2025 12:36
field_ref, "comparing function", None
)
if violation_detected:
reason = format_guardrail_error_message(field_ref, "violation check", None)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to find a better validation result message. If I understand it, right now it will look something like: "Input data didn't match the guardrail condition: [MyParam] violation check". It doesn't make a lot of sense for the agent developer.

@ctiliescuuipath ctiliescuuipath merged commit db612dc into main Dec 16, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants