Publishing Fails due to In-Island Transaction Check

OKomili · October 28, 2026, 8:55pm

Summary

I’m unable to publish a new build because the In-Island Transaction check is failing every time. I was able to publish an updated build last night just fine, but today it’s failing despite no changes to the Verse code being made. I’ve tried 3 separate private versions with a successful memory check on each.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Make a private version and run memory test
Publish the game

Expected Result

Successful publish

Observed Result

Unable to publish an update

Platform(s)

PC

Island Code

9621-3035-2804

Upload an image

Bug-Reporter · October 28, 2026, 8:59pm

FORT-1181959 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

OKomili · October 28, 2026, 9:04pm

FYI I just found another bug report someone posted on the wrong forum, so this issue seems to be more widespread than just me. I also see 3 people on the UEFN Discord server reporting the same problem.

In-Island Transactions Failed open in new window You can't create a new release with this version because it has in-island transaction errors. Create a new version in UEFN that resolves the issues, then try again. Issues and Bug Reporting (Unreal Engine)

Summary yesterday i release a new map, everything was fine, today i wanted to publish a new versions since i fixed some bugs, i didnt touch at all the inslands transaction verse code, and no matter what i try, i created over 5 new versions, i get inslands transaction failed on the portal and cant publish What Type of Bug are you experiencing? Other Steps to Reproduce i just created a new version fixing some envinroment bugs Expected Result the version should be fine to publish and no inslands…

OKomili · October 29, 2026, 12:08am

For those struggling with this… It seems to be back to normal and I’m able to publish again. Note, any new private versions you made earlier are not retroactively being processed, so you’ll need to make a new private build and memory test it again.