Disconnect your receiver from the network and try. I'll bet your timers aren't there anymore....
repeatedly people have deleted items from their receivers and the content is not updated at DO/DRA until after you do a refresh ... this may not have happened to you, but it has happened to others.
And its not just because you are on a static page (refresh), but because DO/DRA polls the data either from the receiver or the receiver sends it out during one of the "update" cycles. either way the data is captured and available to Dish on at least two points (backend 1 & front end the other) of the DO/DRA to/from the user.
the key would be Dish having the ability to export and import the list in some form for the user. Save as XML / Restore from XML. Then the dish server would have to communicate this to the receiver at its next planned update time.
There would also need to be good conflict resolution .. ie.. user X changes timer Y 5 minutes ago on the web site ... then goes to his receiver and changes the same timer Y 3 minutes ago... most recent change wins? and dish would then hopefully explain "Timer Y was not set from DO/DRA because timer y was more recently updated on the receiver ..."
As to cache on the whole ... If they were not using a cache of some sort, then every time you would connect to DO, and on every change of the page, there would be a lag whilst the DO front end waits for the back end collection of data (user account permissions, packages you subscribe to, current content on your drive)
additionally with out the cache of information, the problems that have been seen with User ID's and what dish currently has listed for them should not have existed ... because they would be pulling the data fresh every time you'd log in ... which it doesn't .... hence when the user account gets corrupted they loose some channels on The Guide .. or days of DRA only, would be on their respective dishXX server and wouldn't have needed to be bumped to a different one for functions to suddenly start working again.