---
title: "Pratham Agrawal (@agrawalpratham) | Hashnode"
description: "ServiceNow & AI Engineer at Infosys | AI Agent Studio, Now Assist & Agentic AI. Read the latest articles by Pratham Agrawal on Hashnode."
url: "https://hashnode.com/@agrawalpratham"
---

@agrawalpratham

# Pratham Agrawal

@agrawalpratham · Mumbai, India · Joined July 2024

ServiceNow & AI Engineer at Infosys | AI Agent Studio, Now Assist & Agentic AI

[Website](https://agrawalpratham.in/)

## Comments

[Thanks, this is an important point. An agent saying “Done” isn’t proof that anything happened. I agree that defining postconditions per action is the right safeguard. A few ways I’d connect it to the platform: In the instructions: make the completion condition explicit, and tell the agent to re-read the record after a write (state, assignment, approval) before it confirms success to the user. In testing: agentic evaluations score task completeness and tool calling, not just the final message. That helps catch runs that “sound” complete but aren’t. After go-live: check the execution plan and its tasks (sn\_aia\_execution\_plan / sn\_aia\_execution\_task) against the actual record changes. Any gap between what the agent reported and what the records show is your failure signal. Supervised mode on write actions adds another check, because a human sees the proposed change before it runs. I may cover postcondition checks as their own post. Appreciate you adding this!](https://hashnode.com/posts/servicenow-ai-agent-mistakes/6ad09136b2ae051939d9ed94/comment/6ad0bd1f53e1c1382bb5f461#reply-6ad0cb2550d1070eb760be5c)

Reply · Article · Oct 15 · [Common ServiceNow AI Agent Mistakes (and How to Avoid Them)](https://hashnode.com/posts/servicenow-ai-agent-mistakes/6ad09136b2ae051939d9ed94)
