# Set Values then navigate to next screen is intermittent **URL:** \ **Category:** Issues / Bugs\ **Tags:** beginner\ **Created:** [March 5, 2024, 5:56am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536 "2024-03-05T05:56:14Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![thorntonp72l3](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/thorntonp72l3/32/170888_2.png) [@thorntonp72l3](https://community.thunkable.com/u/thorntonp72l3)\ **Post date:** [March 5, 2024, 5:56am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/1 "2024-03-05T05:56:14Z")
Hi, I am wondering if there is a bug here that when you set/save a whole bunch of stored values before navigating to the next screen. When I first put the blocks in, it seems to work then after a while it stops. It just does not navigate to the intended screen. I.E. ![thunk_99](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/c/9/c9055d3f06218bd5b5f3373e219c1e2e1821df30.png) Example save block ![thunk99_a](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/4/1/41dcd83935358615a149296c5b04f68f317d79a6.png) The problem with this not working, is that the user then has to save the page variables first, then press another button to exit. I would have thought that this should work. Well it does sometimes. Thanks, Paul ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [March 5, 2024, 6:39am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/2 "2024-03-05T06:39:50Z")
When you call a function, Thunkable does not pause the rest of the code. So if you stack function calls and then have a navigate block below them, the navigate command will likely happen before those functions complete. That’s especially true if you are using stored variables which are very slow. ---
**Author:** ![thorntonp72l3](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/thorntonp72l3/32/170888_2.png) [@thorntonp72l3](https://community.thunkable.com/u/thorntonp72l3)\ **Post date:** [March 5, 2024, 6:57am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/3 "2024-03-05T06:57:37Z")
Thanks Tatiang, The problem here though is that the navigate component does not get called. So a little confused ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [March 5, 2024, 7:47am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/4 "2024-03-05T07:47:46Z")
Sorry, I misread what you originally wrote. Is it possible to share a link to the project? ---
**Author:** ![thorntonp72l3](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/thorntonp72l3/32/170888_2.png) [@thorntonp72l3](https://community.thunkable.com/u/thorntonp72l3)\ **Post date:** [March 5, 2024, 9:12am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/5 "2024-03-05T09:12:33Z")
No worries. It is hard to explain. I have setup a real simple test app, now when you first run this it works fine, but go back and forth a few times then it stops going back to the first page [https://x.thunkable.com/copy/ec337c6a98b3b0dbef05972e580b45a6](https://x.thunkable.com/copy/ec337c6a98b3b0dbef05972e580b45a6) Thank you ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [March 5, 2024, 4:17pm UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/6 "2024-03-05T16:17:41Z")
It doesn’t work at all for me, even the first time, on an iPhone 13 Pro. You’re referencing a variable on screen 1 that hasn’t been defined yet. And on screen 2, you need to check for a null value for your stored variables. Try this instead: [https://x.thunkable.com/copy/6cfae13e6934314272d00db7ea3c0ca5](https://x.thunkable.com/copy/6cfae13e6934314272d00db7ea3c0ca5) ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [March 5, 2024, 4:30pm UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/7 "2024-03-05T16:30:55Z")
We’re happy to help investigate this issue more, @thorntonp72l3. Thanks for raising it. Can you confirm all of these functions are completing upon the click event? An easy way to debug this would be to add a label after each function to show the previous function has completed. Thank you! > [@thorntonp72l3](#): > > I.E. > ![thunk_99](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/c/9/c9055d3f06218bd5b5f3373e219c1e2e1821df30.png) ---
**Author:** ![thorntonp72l3](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/thorntonp72l3/32/170888_2.png) [@thorntonp72l3](https://community.thunkable.com/u/thorntonp72l3)\ **Post date:** [March 6, 2024, 1:29am UTC](https://community.thunkable.com/t/set-values-then-navigate-to-next-screen-is-intermittent/2874536/8 "2024-03-06T01:29:34Z")
Hi All, Yes so the mockup one I did was fairly lazy. Sorry, but what I have done is create/modified the same one to make it more realistic. [https://x.thunkable.com/copy/82f9001bfddeb940743efecfad80f96f](https://x.thunkable.com/copy/82f9001bfddeb940743efecfad80f96f) So I know what the problem is, which is okay I guess but I still feel this is a bug. If you set the Stored variable with a entry from a blank input field it then stops working and you cannot even recover it as in force the stored variable to contain something. I have to actually change the variable to something else hence I now have 13 on the end of my variables. ![thunk100](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/2/1/21d2af745a29064f0affcedd3ed8902ca84a87bf.jpeg) Thank you, Paul