First, thanks for a great feature. Definitely valuable.

I often schedule emails to send for when I specifically won't be on my computer. When I go to check sent emails, it's usually several hours or a day later or several days later and if the date didn't parse correctly, my response to a conversation is now late (or mistimed).

To know how my date will be parsed ahead of time, I have to go test my date in Testing Resources (more time wasted than just typing the date in standard long format). So my own solution for now is to memorize and use the standard long format. But I really like the flexibility of more casual date descriptions, especially when typing a trigger on my mobile (switching keyboards for symbols is cumbersome).

Solution 1: I can train myself to be better at knowing the correct form of more short parseable date formats. But mistakes are still possible.

Solution 2: Build something like the "Parse Date" feature in "Testing Resources" into the draft writing or draft checking workflow.

Solution 3: When the script runs and finds a draft email with the trigger, it replaces the user-entered date text with script-generated date text in a standard long format.

The user can check drafts to see that dates parsed correctly, can revise the date, can revise the draft, etc. without any new steps in the original writing process (ie new dialogs, new clicks, confirmations, etc)

Further, the script add a label or subj text that would highlight drafts that have been modified by the script. Currently, delay-send drafts and plain old drafts are mixed together so it's more difficult to go find the ones you want to double-check for correctly parsed dates.