# Serializing/Saving window takes more than 10 minutes

**URL:** <https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834>\
**Category:** Ignition\
**Created:** [January 14, 2014, 6:16pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834 "2014-01-14T18:16:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![cacordova](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@cacordova](https://forum.inductiveautomation.com/u/cacordova)\
**Post date:** [January 14, 2014, 6:16pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/1 "2014-01-14T18:16:37Z")

</div>

Hi,

Just wanted to ask, we’ve had an issue about sometimes when we are saving its takes more than 10 minutes to save and it stays on the “Serializing Window” process.

On one of our windows where savings takes longer, we’ve used a lot of templates and on the other window we used a lot of objects such as tanks, buttons, pipes etc. and we have one table where we get the tag history for a one or two tags.

What could be the cause of this issue?

Thanks

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 14, 2014, 6:41pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/2 "2014-01-14T18:41:55Z")

</div>

Usually the cause is that you’ve got a large dataset loaded up somewhere on that window… (e.g. you saved the window with a bunch of data in a table).

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [January 14, 2014, 6:44pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/3 "2014-01-14T18:44:03Z")

</div>

Yea, likely you are saving a lot of data (in datasets) that is pulled into the window in the designer.

---

<div class="post-metadata">

**Author:** ![cacordova](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@cacordova](https://forum.inductiveautomation.com/u/cacordova)\
**Post date:** [January 14, 2014, 8:11pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/4 "2014-01-14T20:11:16Z")

</div>

Hmm… Ok… so what should i do?

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [January 14, 2014, 8:30pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/5 "2014-01-14T20:30:12Z")

</div>

In one of the slow windows look at the datasets in the window. Look for a dataset with a lot of data in it.

A source of large datasets in windows is database queries. If you have a database query generating a large dataset then disable the Gateway communication and delete the content in the dataset and then save the project – this will save the window without the large dataset.

If there are no large datasets in the window then maybe the problem is something else.

---

<div class="post-metadata">

**Author:** ![cacordova](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@cacordova](https://forum.inductiveautomation.com/u/cacordova)\
**Post date:** [January 14, 2014, 10:59pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/6 "2014-01-14T22:59:48Z")

</div>

[quote=“nmudge”]In one of the slow windows look at the datasets in the window. Look for a dataset with a lot of data in it.

A source of large datasets in windows is database queries. If you have a database query generating a large dataset then disable the Gateway communication and delete the content in the dataset and then save the project – this will save the window without the large dataset.

If there are no large datasets in the window then maybe the problem is something else.[/quote]

Tried this, but its still taking too long to save. 😐

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [January 14, 2014, 11:07pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/7 "2014-01-14T23:07:12Z")

</div>

Did you find any large datasets? How many rows and columns?

---

<div class="post-metadata">

**Author:** ![anna](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@anna](https://forum.inductiveautomation.com/u/anna)\
**Post date:** [January 14, 2014, 11:15pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/8 "2014-01-14T23:15:38Z")

</div>

In your email you also mention heavy use of templates and Symbol Factory objects; Did you check how parameters are passed to those templates / objects (do you have UDT type parameters or mostly string parameters holding paths?)

Symbol Factory objects are vector graphics; if you have a lot of them, without flattening any, that can contribute to the issue too.

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [January 15, 2014, 12:00am UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/9 "2014-01-15T00:00:20Z")

</div>

One idea is to make a copy of your window and save the project. Then start deleting things from the copy window and saving each time you do. This can help you narrow down exactly what in the window is taking a long time to save. When the window saves quickly then you know you just deleted the thing that took a long time to save. Then look into that thing to see if you can find out why it takes a long time to save.

---

<div class="post-metadata">

**Author:** ![cacordova](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@cacordova](https://forum.inductiveautomation.com/u/cacordova)\
**Post date:** [January 15, 2014, 5:50pm UTC](https://forum.inductiveautomation.com/t/serializing-saving-window-takes-more-than-10-minutes/7834/10 "2014-01-15T17:50:55Z")

</div>

Ok I’ll do that. Thank You.
