Couple questions here...
First.. Why are you using cfschedule to just send an email? This could be more easily done in the form processor.
Second... If you are using the cfschedule to do it what happens if 2 people submit the form at the same time?
As for the email, check in the undelivered folder on the server for the email. If it was unable to be sent it would be in there.
It is for an inventory system. The form includes a return date for borrowing an item. When they submit the form, the cfschedule will use the return date from the form variable as the enddate attribute on the cfschedule. So...the day their equipment is due back, they recieve an email.
My code does not reflect this yet, I hardcoded a date for testing purposes.
And actually, I got it to work. I had to change the URL attribute to an absolute link instead of relative.
By the way....see my other comment first. - is there a better way to do what I mentioned in my other comment?
I wouldn't do it this way at all. What happens when you have 1000 items, or even 2, due in the future? You would have a scheduled task for each item. This would create a management nightmare that I wouldn't want to deal with.
I would just run a task each day to poll for items doe that day and then send an email. Much cleaner approach and far less prone to failure. You could easily write code to deail with issues, resend emails, and generally recover from failures with little effort.