I am getting the same thing in my game. It's totally frustrating. I also took screenshots, have a save and a debug txt file. I couldn't find anything of note in log file. I could upload all of this if it's needed but i don't have dropbox or something like that where I can upload stuff.

The problem is, a single game of FE takes a long time, especially on a large map, normally much longer than a single multi-hour session, and you can't easily keep FE open while doing other stuff or it will eventually have a DX error.  So you are not just discriminating against "save scummers", you are discriminating against people who don't want to spend 10 or so hours in a day just to finish one game.  Then there are those who don't have so reliable power, and making AI players jump ahead after a power failure is hardly justice.

wish i would have saw this before installing 1004

Omg, it happens to me to on challenging!

i remembered one of the wonders, and tomorrow upon loading later turn it happened to another!

gawd, please frog, fix hat asap!

I've noticed this a few times too (AI finishing everything in queue when you load), but I'm certain that it doesn't happen all the time, which is why it's so hard to track down. It seems like there are some conditions that has to be met in order for it to happen. Perhaps when the save happens during the AI's turn or something... so when you load it up it doesn't sync correctly. Or maybe there's some bug going on with the AI's queue.

I generally Ironman the game and only load between gaming sessions, so I don't really notice this effect too often... but this may be the reason why people are having so much trouble with the AI.

You should have checked they're gold reserves too, but nice find.

Sincerely
~ Kongdej

Excellent; this is one of the more annoying bugs in the game. Thanks for actually providing support and patching the game and all, Derek/Brad/etc;)

Now about that 1.01 patch... *cough* *cough*

Thanks a lot.  I found this very annoying.

So.... when I cheat the AI cheats too...?

 NO F***ING FAIR!

BTW: I think FE is a great way to continue the FfH legacy - I love the game and I loved FfH!

Couple questions for the OP (and others confirming this bug):

1) Did you see the Great Mill in queue with lots of turns remaining before the reload?

I have seen the announcements not always take place when something wonderful gets built but then get announced when starting up the game.  I'm not saying a bug didn't take place but the more details we have the less likely we are to waste developer time chasing the wrong ghosts.

2) For everyone seeing entire queues instantly cleared on restarts ARE YOU SEEING ALL THOSE BUILDINGS NOW LISTED on the structure list for that city?

I've never seen a city suddenly built up in a turn (been around since they announced they were atoning for Elemental).  Bugs happen but more details would help a ton.  The AI's often change their queue lists.  I've seen production queues change radically at times when the AI rethinks it's strategy but not seen those disappeared queued buildings get built.  Also some info doesn't appear to be loaded up when restarting a game until a turn goes by...example, the diplomatic plus and minus list.  Reloading a game could easily be a trigger for the AI to "rethink" what it is doing and wipe it's list.

I'm not saying these things aren't bugged. Bugs of this magnitude would be game breakers. Just that we need to nail it down with the full details or false bugs will lead to real bugs not getting fixed.

I've been in beta since near the start and not seen much in the way of confirmed game breakers.  Two crash to desktops ever, not witmessed sudden seismic shifts in power. Concerns that reloading might be confusing the AI into losing turns with sudden shifts in it's thinking (even the best AI's need a lot of help against real players and can't afford such schitzophrenic shifts).  Lots of little bugs but three accusations and misunderstandings for every real one.

Some real bugs:

--XP operating systems seem to have a confirmed major memory leak (true bug). The leak isn't universal though.  Windows 7 (at least with my main stream slightly dated rig appears to have not have the problem, at least not to anywhere near the same degree).  Windows 8 has it's own issues.

--Opponent scores suddenly jumping has been a common complaint and could be a hint towards a game breaking problem requiring major changes in the coding. More likely reality.... I have seen scores change abruptly when the AI "rethinks" it's strategy and sends it's stationed units out from the towns housing them. Watch how fast their scores change when they go to war.  Suddenly faction scores change wildly! Why? Because it appears that faction score is your military power ranking and the real bug may be that units in towns don't get added to the score. (These numbers only get checked between turns). There may be more to it than that...heroes may always count or player troops may be scored accurately but not AI's or certain AI's, etc. The point being that accusations without all the details can lead to looking in the wrong directions.

Couple lesser bugs...

--Pioneer quest that doesn't give a pioneer if you fight instead of pay for the unit...confirmed bug...has it been confirmed that no pioneer is given if there is room for the pioneer to join your group?  In other words, is the bug that there is never a pioneer when you fight or that a pioneer doesn't get added unless there is a space in your group?

--Shadowbolt doesn't get Warlock or other damage % adds although the tooltip shows as if these bonuses will be added.  This is a tooltip bug.  Shadowbolt is working as intended (based on a reply many months ago).  There is no elemental resistance to shadowbolt so they took away it's bonuses to keep it from being over powered.

--Probably the biggest set of bugs in the game is how horribly out of date the tooltip info is.  The game has changed a ton in many little ways with pretty much all the tweaking being for the better.  The obsolete tooltips cause a great amount of frustration (even to those that know the real info at times) and frankly leads to a lot of misinformation being handed back to the dev's. Cleaning these up might be a big job but is an attainable way to help us all.

(Edited for typos).

Here are my steps to profit:

1. Read about the issue in the forum post.

2. Reproduced it on my pc.

3. Looked in the code to see why it was happening.

4. Got confused.

5. Asked Sarah (one of our devs) to check it out.

6. Problem was fixed.