Hi,
I noticed an inconsistency in the Softr Ask AI feature and I’d like to clarify whether this is expected behavior or a bug.
Using the same dataset:
When I ask “Get the details of the last leave request I submitted”,
→ I get: “There is no information available in the current dataset…”
But immediately after, when I ask “List my leave requests”,
→ it returns all my leave requests correctly.
So the data clearly exists, but queries like “last leave request” or “last two leave requests” fail, while general listing works fine.
Same table, same records, same user context.
Is this intended behavior?
Is there a known issue with Ask AI’s filtering or ordering logic?
I think I finally found the culprit — and surprisingly, the issue wasn’t on Softr’s side, it was on mine.
Since nobody replied, I thought “okay, if no one else has this problem, then it must be me,” so I started digging again.
Turns out the problem wasn’t Ask AI at all.
I had an old UI-level filter applied on the table.
Visually it still looked fine, but after I made a few schema/field changes in the database, that old filter silently broke Ask AI’s context resolution.
That’s why:
“get my last leave request” → failed
“list my leave requests” → worked perfectly
Same table, same user, same data — but inconsistent behavior.
After I removed the old filter and recreated it from scratch, Ask AI immediately started behaving correctly again.
Queries like “last request” or “last two requests” now work without any issues.
