Hmmmmm. Have a look the file recovery options: [https://easyeda.com/forum/topic/EasyEDA-NOT-Saving-My-PCB-0bb57c2f15fd4524be548d51be46b85f](https://easyeda.com/forum/topic/EasyEDA-NOT-Saving-My-PCB-0bb57c2f15fd4524be548d51be46b85f)

@andyfierman Many thanks. I went to the file history for the schematics and found the versions from Tuesday and today (10 & 11). As I record what I do when I do it, I knew that I had changed two capacitors and removed a plug on the schematics in question on Tuesday, so recovered version 10. It's now back to how it should be. As I can't see the changes between versions without restoring them, I don't know if versions 11 was the same as version 9 but I suspect it is. As to whether the PCB is a module or a PCB, I did not intentionally save it as a module, but as it is an Arduino Shield, and I used the R3 version highlighted on your home page over a year ago, if that was a module then maybe my "new" PCB is also a module. However, this is the first time that I have observed this schematic save issue and I've been wotking on the PCB for about a week now. The PCB is the concatination of 3 schematics, and this is the only one of the three that seems to have "lost" the changes that I made on Tuesday. The other two are still fine.

@andyfierman PS The time stamps are confusing. All the work on versions 10 and 11 was done between 7am and 10am, not 5pm as the time stamps woulod have me believe.

Glad you're back on track. I haven't done much work with modules but it could simply be that if you opened a module then edited it and saved it, it would automatically be saved as a module rather than a PCB as you intended. You can always do Save As... into a temporay project to keep a separate backup in case you are worried that a restore might overwrite something. :) If you have time, please post a bug report about the timestamps.

@andyfierman Will do. Probably tonight. I need to do a bit more investigation but I suspect the time stamp is the time at the server, not the time at origin of the save? As I say I need to dig a bit.

@NuttyProfessor47 Hi, very sorry for this issue, the can't save version is released by accident, we switch a normal version immediately, but still some users will get this version. when you finish your work in this version, you can export the design as easyeda source file: [https://docs.easyeda.com/en/Export/Export-EasyEDA-Source-File/index.html](https://docs.easyeda.com/en/Export/Export-EasyEDA-Source-File/index.html) and open it at the new version. or please find your file at "Document Recovery" after updating to new version: [https://docs.easyeda.com/en/Introduction/Basic-Skill/index.html#Document-Recovery](https://docs.easyeda.com/en/Introduction/Basic-Skill/index.html#Document-Recovery) We apologize for any inconvenience again.

@andyfierman Hi Andy. I've checked local time against the timestamps on file history twice now, this morning and this evening. Local time is now UTC +1 whereas timestamps for a save are UTC +8, placing the origin of the stamp in China, Indonesia, or western Australia, so I think my hypothesis is correct, the timestamp is time at the EasyEDA servers. I am still happy to submit a bug report if indeed it is a bug, or a feature request if the need is to add functionality to take time from the computer from which the save is requested. I'd welcome your opinion about the most appropriate option. As for the save error, it seems an incomplete build got out and I was just unlucky.

Hi The time stamp issue is because of we using the EasyEDA server time to record, we will try to solve this issue, too many time zone, it is hard to solve perfectly. thanks