T
td
I'm using my employer's Outlook web access. If I take more than a certain
time (I think 10 minutes) composing an email, then when I hit send I get a
message that I need to log back in because my session has timed out (or
something like that). When I do log back in, the message I had been working
on is deleted.
I saw a short thread about this back in 2005 and 2006. Has there been any
change in this since then? Is there any fix for this, or does anyone have
any information on why this can't be fixed?
FYI, I have once been able to successfully migrate back (by hitting my
browser's back button) to my composition page to retrieve my work. But other
times this has not worked. When it did work, I had to respond to a message
box telling me that the the browers had to re-post data to load that page (or
something similar). I clicked "ok" or "yes." So if you find yourself in
this position, give that a try if nothing else.
If this is still a problem, then I have to say to Microsoft that this is a
completely unacceptable design issue. You can't destroy your client's work
because they took "too long" to compose a message, particularly without any
warning whatsoever.
time (I think 10 minutes) composing an email, then when I hit send I get a
message that I need to log back in because my session has timed out (or
something like that). When I do log back in, the message I had been working
on is deleted.
I saw a short thread about this back in 2005 and 2006. Has there been any
change in this since then? Is there any fix for this, or does anyone have
any information on why this can't be fixed?
FYI, I have once been able to successfully migrate back (by hitting my
browser's back button) to my composition page to retrieve my work. But other
times this has not worked. When it did work, I had to respond to a message
box telling me that the the browers had to re-post data to load that page (or
something similar). I clicked "ok" or "yes." So if you find yourself in
this position, give that a try if nothing else.
If this is still a problem, then I have to say to Microsoft that this is a
completely unacceptable design issue. You can't destroy your client's work
because they took "too long" to compose a message, particularly without any
warning whatsoever.