[ Server ] Error: column "version_hero_type" cannot be cast automatically to type enum__pages_v_version_hero_type

[latioms]

Describe the Bug.

I tried to put the list of heros. Then I changed my mind and got this error

Reproduction Steps

1- Udpate the src/heros/config.ts :
{
label: 'Low Impact',
value: 'lowImpact',
},
{
label: 'Hero 39',
value: 'hero39',
}
2- Press Y in the console after seeing a message (without reading)
3- removing the "Hero 39" object in the options
4 got this error

Environment Info

Payload 3
nextjs 15
postgresql 17.2

[Aaron-Darklake]

Same problem here with the newest update of "with-vercel-website" template.

[mxvsh]

Same issue here, I tried creating hero section and it broke.

[TheOrdinaryWow]

same here

[hatchli]

Same problem

[DmacMcgreg]

Yikes I just lot a ton of data because of this issue... BEWARE. Do not ignore the data loss error here.

[latioms]

Me too 💔 Le ven. 7 mars 2025 à 10:06 PM, Dmac ***@***.***> a écrit :

…

Yikes I just lot a ton of data because of this issue... BEWARE. Do not ignore the data loss error here. — Reply to this email directly, view it on GitHub <#10790 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARPJM5TDFWBM7CCTJDD44R32TIC5LAVCNFSM6AAAAABVZ4UOMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGQ2TQNRSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: DmacMcgreg]*DmacMcgreg* left a comment (payloadcms/payload#10790) <#10790 (comment)> Yikes I just lot a ton of data because of this issue... BEWARE. Do not ignore the data loss error here. — Reply to this email directly, view it on GitHub <#10790 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARPJM5TDFWBM7CCTJDD44R32TIC5LAVCNFSM6AAAAABVZ4UOMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGQ2TQNRSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Rot4tion]

i face same issue with enum field

[2Senn]

Can anyone suggest a fix? it happens quite often for me

[dcos96038]

same problem

[GinoNovello]

same issue

[Saissaken]

also happening here, anyone knows which was the last payload version where this was working fine?

@r1tsuu seems like this could be drizzle related? drizzle-team/drizzle-orm#2751