Can't publish or Launch Memory Calculation to update my already published island

Summary

I made a small update on my island and since 38.10 i get this error message everytime i want to Launch Memory Calculation. I did restart UEFN, i waited 2h, I even waited 12h today tp try it again and same error. I get Parallel upload flow is already running first and then i get the Internal error after.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Launch session in Edit. Going back to UEFN and click on Launch Memory Calculation. And the error happens. I get Parallel upload flow is already running first and then i get the Internal error after.

Expected Result

No errors like usual and i can continue in Creator Portal to publish my map.

Observed Result

See the screenshot i posted.

Platform(s)

Windows

Island Code

6005-4587-3961

Upload an image


Additional Notes

I did a Fixed Validation Issue, an Update Redirector Reference, a Project Validation first and every time and i still have the same issue. I also removed the Island Settings and added a fresh one with the same settings because i had a previous bug related to that issue.

I’m having the same issue.

2 Likes

I am also getting this issue but only specifically on one map and i tried everything and cant seem to fix it. At some point it mentioned an error about localization which i found out its the language files, but even running auto localization didnt fix the issue.

1 Like

I am experiencing the same issue when i try to Launch Memory Calculation
Map code: 1634-7906-8364

1 Like

Got this error a few times this morning. I hadn’t noticed the “Build Localization” checkbox on the private version upload menu before today so I assume that could be the cause. First thing I did was close everything and restart the pc. Second, I went into my project settings and disabled all of the language localization settings just to see what would happen and immediately the next memory calculation was successful.

1 Like

(post deleted by author)

s

I haven’t made use of localization or translation in the map I tested this on so I have no idea if it will affect any translated materials. You might have to duplicate your project and do some testing for that.

So i got the error also in my other project, and it was the localization for this file that gave me the error

zh-Hans/HIDEnSEEk.po

So i removed all the localization manually in my computer, redid it just for English and French, had to restart UEFN and now was able to published, will try again in my previous project.

Well, i did the exact same steps for my previous project and still got the same errors.

This is what the AI said about my issue @epic , if that helps

“UEFN publish fails with ‘Parallel upload flow is already running’ and ‘Internal error’ due to a stuck Valkyrie backend process (module ID: abe69457-42a0-27f0-302d-5db05b39a738), blocking new builds despite clean localization and project state.”

same thing just happened to me

I have the same problem and don’t know how to solve it.

2 Likes

I unpublished my island just to try and get the updated version to bypass this error but still throwing the same error. just waiting patiently on a fix.

1 Like

i am getting the same issue on one of my projects as well. tried restarting my uefn and fortnite and keeps giving “Parallel upload flow is already running” Error hope this is fixed soon..

1 Like

I had this problem, I reset my Native language and languages to translate to their defaults, I also disabled automatically build localization.

image

2 Likes

Can confirm having the same error, will try to disable auto localize build now and see if it works.

Thanks for the info guys ! :slight_smile:

All the tips did not help, any ideas how to fix this step by step ? :slight_smile:

1 Like

Update: what helped resetting all the localization settings to default, closing uefn, manually dleeting the localization folder from the project, launching it again and pressing calculate memory after starting

4 Likes

Just tested with 38.11 that was released today and still have the same error…

1 Like

same

1 Like