In a Single choice, I am asking to enter time and have given a few options. It is open for the user to enter a time of their choice. If the Slots for Selection are 09:00, 09:45, 10:30, 11:15 and the user enters 12:00, it fails extraction [Capture] Field extraction failed. Input: 12:00 If the user enters 11:30, the extracted value is 10:30 [Capture] Field validation successful! Extracted: "10:30". Input: 11:30 How? https://cdn.discordapp.com/attachments/1227319526316834991/1227319526857904138/image.png?ex=6627f961&is=66158461&hm=e0bd66032f0395658b46438ad39a214f665dd4308199dd57e6b8f72778269389& https://cdn.discordapp.com/attachments/1227319526316834991/1227319527180861510/image.png?ex=6627f961&is=66158461&hm=b729b539106b9db8732fcfd1308efc3d18bcfd72f31022e9f907a8636a0bc67d&

do you get the same in the emulator? you can check the logs & bottom debugger panel; and you'll see how/why it extracts 10:30

@rich-battery-69172 cannot in the emulator, there are calls to Google API that fail but in the logs, I can see this > [Capture] Transformed the extracted value [Capture] Field validation successful! Extracted: "10:30". Input: 11:30

@limited-pencil-78283 can you change the capture type from "Single Choice" to "Raw Input" , then use an AI Task to parse the time? The reason why it behaves that way with the "Choice Capture" is because it will try to match one of the provided options. It will perform fuzzy matching and try to fit the time that is closest. In the case of 11:30 vs 10:30, there is a single character difference. Here's an example below. of how to achieve a better extraction with Raw + AI Task: https://cdn.discordapp.com/attachments/1227319526316834991/1227352614623121438/image.png?ex=66281832&is=6615a332&hm=7d8839c26ce1223d350c235fca31eef90a6371df71ee04c7dafa029f42888c5b& https://cdn.discordapp.com/attachments/1227319526316834991/1227352615004672100/image.png?ex=66281832&is=6615a332&hm=e258221ab2271c3c5dae5bd2ea25380b3203f3e5394e61b56315ea65fcb25692& https://cdn.discordapp.com/attachments/1227319526316834991/1227352615315181608/image.png?ex=66281832&is=6615a332&hm=e38fda56433ed8ffc3afc0f91e885e722a7d2b5daf7307d164916b0aed380736&

@sly - Running everything on AI is burning cash. There has to be a better way to manage this

You know capture cards are wrappers around GPT right ?

Sly's method is solid indeed but a simplified alternative could be to simply add more timeslot options (in your dropdown list).