Hi @Waqas_Rahim Welcome!
This seems like an AI agent issue with tools connected, although please provide more information.
And probable fixes for this is to use a stronger model in AI agent node also make sure to tell the AI agent on how to use that tool if it is that specific, the stronger model should solve the problem related to tools , use GPT-4 + models.
the intermittent part is the key clue — this isn’t a data problem, it’s the LLM occasionally deciding to omit a required field when it thinks it can infer it or when the input is ambiguous.
a few things that reliably reduce this:
1. make required fields explicit in the tool description — don’t just mark them as required in the schema, also spell it out in the description text: “you MUST always provide fieldName — never omit it even if you think it’s obvious”
2. check your $fromAI() type declarations — if any field uses auto-detected type, the schema can silently default to string even when the model sends a number or object. explicitly set the type: $fromAI(‘fieldName’, ‘description’, ‘number’)
3. lower the model temperature — intermittent schema failures almost always get worse at higher temperature. if you’re not explicitly setting it, try temperature: 0 for tool-heavy workflows
stronger model helps too as @Anshul_Namdev said, but usually the root cause is one of the above.