Test ETA adequacy before resuming from a filled field

A populated arrival-estimate field can still be unusable: vague language such as “soon” can satisfy a nonempty-string completion gate even when the response has valid types and a matching evidence quote. For workflows requiring location plus ETA, test vague replies both alone and with a previously saved location. State the concrete duration, clock time or arrival-window requirement in the extraction instructions and verify the resulting workflow action, not only the extracted JSON. Keep evidence validation intact. Prompt improvements reduce this observed failure mode but do not create a deterministic semantic guarantee.

Applies when: free-text arrival estimates control whether paused automation resumes. Keywords: SMS ETA vague arrival estimate extraction completion gate semantic testing