ERR_JOURNEYVERSION_107 — All journey versions fail to deserialize in dev sandbox (sandbox-level corruption) | Community
Skip to main content
U
uk685
Level 2
April 20, 2026
Question

ERR_JOURNEYVERSION_107 — All journey versions fail to deserialize in dev sandbox (sandbox-level corruption)

  • April 20, 2026
  • 1 reply
  • 15 views

All journey versions in our `dev-beta-testing` sandbox return ERR_JOURNEYVERSION_107 ("journey version can't be deserialized"). Even brand-new minimal journeys (Audience Qualification → End, no email/actions) fail immediately. The sandbox was previously working — we have deployed and stopped versions. The version store appears corrupted: `GET /journeyVersions?journey=<uid>` returns the same 10 versions for every journey regardless of the filter. Other sandboxes in the same org work fine. Requesting guidance

    1 reply

    I
    IamCGK
    Level 2
    April 20, 2026

    Hey ​@uk685 

    It is likely that your sandbox might have been corrupted. Although, I see a post which mentions about this exact error where they got it resolved by addressing the required attributes within the actions.

    Since you’re saying this happens for even simple journeys, then I’d suggest deleting those set of journeys (which causes error) and creating new ones to verify the behavior.

    If the above doesn’t work, then I’d suggest resetting the sandbox (based on the level of rework) or exporting that sandbox entirely to a different empty sandbox like mentioned in this documentation. Hope this helps!

     

    Cheers,

    Ganesh Kumar C

    Terms & ConditionsAccessibility statement

    Loading footer...