An agent filled in a JSON field, but the proposed change did not reach the review queue. Does Busabase validate JSON before a change request is submitted? Where should the value be fixed and resubmitted? Does the same rule apply to YAML fields?
Yes. Busabase checks a JSON field's syntax before it creates the Change Request. If the agent sends invalid JSON, the submission is rejected and there is no pending item to find in the Inbox. YAML fields follow the same idea: they must parse as valid YAML before submission.
Have the agent keep the error from the failed write, correct the value in its proposed payload, validate that JSON or YAML locally, then submit again. Do not try to approve an invalid item that never reached the queue. For JSON, common issues include missing quotes around keys, trailing commas, and unescaped quotes inside strings; a syntactically valid object can still be wrong for your business rules, so a reviewer should inspect its meaning after it appears in the Inbox. If you have a sanitized error message, it can help locate the failing field.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in