Getting verse persistence issues on all of my maps, even ones without verse.

Summary

When publishing a new revision of my recent island in collab with FaZe Replays, I noticed a verse persistence check was in progress before I could submit for review, eventually it gave a validation error that simply said the server timed out and appeared to be “cook” related. Upon posting to Twitter, a few others were having the issue, curiously, its happening to all of my other maps that DO NOT have verse at all, making publishing on any of my maps currently impossible.

Also, if I roll back any of my island codes to a previous one, even if it claims there are verse errors despite not having verse or verse devices in some of my maps, the issue magically goes away for that specific version indefinitely. It is very strange.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Creator Portal

Steps to Reproduce

Creating a new version of a project to publish or selecting an older version of a project than the current active version, even on projects with no verse.

Expected Result

No verse persistence checks on existing islands with no verse or not getting server timeout errors on new versions

Observed Result

I create a new version on any of my maps, even ones with no verse, calculate memory, and regardless of the project, gets stuck checking verse persistence only to persistently fail validation with a timeout of 120000ms as a result of a cook error. Causing all maps to be unpublishable on new (or old) versions for now

Platform(s)

PC

Island Code

7582-7422-2517

Upload an image



Video

Additional Notes

As noted before its happening to other users as well as evident by my comments on twitter, however some people are also claiming they are fine so I am unsure what to do.

This affect also my projects, same issue

1 Like

Same issue here. It’s affecting our projects that don’t even use Verse too.

Thanks, is this still occurring today for you @EDMIRE ?

For those whom it’s also occurring to, could you please share your island codes that are failing to this issue?

Its hit or miss. Some projects it does it, but now the project in question works fine sometimes when I make new versions so for now I WAS able to get a new version out, I cant say the same for other people though.

This issue should now be resolved. Can you confirm on your end that publishing works? @EDMIRE

FORT-911625’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.