# Project chages are not saved

**URL:** https://community.thunkable.com/t/project-chages-are-not-saved/17011
**Category:** Questions about Thunkable X
**Created:** [February 13, 2018, 2:12pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011 "2018-02-13T14:12:25Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![losmobilos](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/losmobilos/32/11983_2.png) [@losmobilos](https://community.thunkable.com/u/losmobilos)
#### Post date: [February 13, 2018, 2:12pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/1 "2018-02-13T14:12:25Z")

</div>

In a quite large project I experience problems saving my changes to the code (blocks), which means that my code is now in a dysfunctional state.

I cannot find a system to the occational succesful save of the project - I am very frustrated right now - but I’m sure there’s a solution.

Please - what can be the problem?

---

<div class="post-metadata">

### Author: ![losmobilos](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/losmobilos/32/11983_2.png) [@losmobilos](https://community.thunkable.com/u/losmobilos)
#### Post date: [February 13, 2018, 3:00pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/2 "2018-02-13T15:00:08Z")

</div>

More testing shows that the problem may well be related to having to many blocks/too large source code: when I optimized some legacy code away I was able to add new blocks that were all saved.

It is easy to spot if the save is performed: if the “Live Test” is running, the app on the device will restart for every saved code change. By adding one block at a time it was easy to see that a limit was reached at some time. Removing code blocks at that time made it possible to add more (new) blocks.

So now the question is: is this analysis valid?

If so - what is the code size limit and how will we know if we have reached it?

---

<div class="post-metadata">

### Author: ![Mark](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/mark/32/18133_2.png) [@Mark](https://community.thunkable.com/u/Mark)
#### Post date: [February 14, 2018, 5:20pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/3 "2018-02-14T17:20:39Z")

</div>

Sorry for the problem. We don’t have any built-in limits on the code size, so it looks like this is a bug. To help us diagnose it, could you send us a share link to your project at the point that it works but adding one more block makes it no longer work? Feel free to send a direct message to me with the link.

Thanks in advance.

-Mark

---

<div class="post-metadata">

### Author: ![losmobilos](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/losmobilos/32/11983_2.png) [@losmobilos](https://community.thunkable.com/u/losmobilos)
#### Post date: [February 16, 2018, 10:05am UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/4 "2018-02-16T10:05:19Z")

</div>

Hi Mark,

At the moment I do not experience the problem as I have refactored some of the code to make it smaller.

However, there might be another issue related to this: Synchronizing source code updates/changes to block are not alwas immediately reflected to the Live Test app.

Maybe the block changes are not saved immediately or even not at all - something holding back the file writing perhaps?

---

<div class="post-metadata">

### Author: ![Mark](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/mark/32/18133_2.png) [@Mark](https://community.thunkable.com/u/Mark)
#### Post date: [February 16, 2018, 5:22pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/5 "2018-02-16T17:22:44Z")

</div>

If you see the problem with the project not saving again, please share your project with us so we can try and diagnose it.

As for the delay in synchronization with the Live Test app, that may also have to do with the size of the project. Again, if you can share your project with us, that might help us track down the issue.

-Mark

---

<div class="post-metadata">

### Author: ![hordearii2013j](https://avatars.discourse-cdn.com/v4/letter/h/f9ae1b/32.png) [@hordearii2013j](https://community.thunkable.com/u/hordearii2013j)
#### Post date: [January 25, 2020, 12:45pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/6 "2020-01-25T12:45:25Z")

</div>

tengo el mismo problema,pero no tengo ni un bloque, no puedo ni ordenar dos bloques que ya se me borra todo!!!

---

<div class="post-metadata">

### Author: ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)
#### Post date: [January 25, 2020, 1:05pm UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/7 "2020-01-25T13:05:15Z")

</div>

¡Hola! Este es un problema conocido en el que el equipo de Thunkable está trabajando. ver esta publicación de @jane

> [@\[Solved\] Jan. 2020 Thunkable X Blocks Update](http://community.thunkable.com/t/thunkable-x-blocks-update-your-feedback/425809):
>
> Hi Thunkers! wave As you may know, creators have been reporting that their blocks screens slowed down a lot when they had a lot of blocks in their app. The good news is, we have just published an update that prevents a lot of this slowdown! This makes a lot of projects more useable. Unfortunately, we are also hearing that some creators are having unexpected problems in their app projects that seem to be related to this update. If you are experiencing something like this, please fill out [th…](https://docs.google.com/forms/d/e/1FAIpQLSf3hY6vwgMt7PALyZbh2CU6GDyFj-ezRWcBpiibpucyZSb1jQ/viewform)

---

<div class="post-metadata">

### Author: ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)
#### Post date: [November 8, 2024, 11:45am UTC](https://community.thunkable.com/t/project-chages-are-not-saved/17011/8 "2024-11-08T11:45:51Z")

</div>


