[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Version skew; What happens after 12 hours?

115 views · 5 likes · 4 posts


Alexbjorlig (@alexbjorlig) · 2024-07-31 · ♥ 1

Our team is testing Vercel version skew with Sveltekit.

In our test project, we have a form you can submit.

Most things seem to work, but something unclear to me is what exactly is supposed to happen when you submit a form from an old version, after 12 hours.

At the moment, the old version seems to be alive despite being older than 12 hours. I hope you can help clarify what the intended behavior is here, thanks.


Swarnava Sengupta (@swarnava) · 2024-07-31 · ♥ 2

[quote="alexbjorlig, post:1, topic:371, full:true"]

At the moment, the old version seems to be alive despite being older than 12 hours. I hope you can help clarify what the intended behavior is here, thanks.
[/quote]

Can you share us more information about what behavior you are seeing? The deployment should indeed remain `alive` and it shouldn't just be blocked to remain accessible. Do you have a screencast / logs which we can refer?

Also note that If you are using SvelteKit, you will need to install `@sveltejs/adapter-vercel` version 5.2.0 or newer in order to [enable Skew Protection](https://vercel.com/docs/deployments/skew-protection#enable-skew-protection).


Alexbjorlig (@alexbjorlig) · 2024-08-01 · ♥ 1

Hi @swarnava 

I have now updated the project to the newest version of the adapter-vercel, and enabled version skew.

I have recorded what happened when I submitted a form, from an expired deployment. You can view the results here:

https://vimeo.com/993331514?share=copy

So I guess the conclusion is that when a deployment is expired, it will route requests to the current deployment.


Swarnava Sengupta (@swarnava) · 2024-08-06 · ♥ 1

[quote="alexbjorlig, post:3, topic:371"]
So I guess the conclusion is that when a deployment is expired, it will route requests to the current deployment.
[/quote]

Hi there,

Thank you for sharing the detailed video. I checked with team and this is currently intended behavior.