Summary
Creating a Full Rig for a MetaHuman Character is accepted by the AutoRig service and reaches the state represented as 75% / RUNNING. Status polling then times out at the configured 300-second HTTP limit. Unreal Editor reports “Server Error”, returns the character to the unbound state, and the asset file remains unchanged.
Expected: the service returns the completed rig data and the character becomes Full Rig bound.
Environment: Windows 11; Unreal Engine 5.8 installed build; MetaHuman Character and MetaHuman Live Link plugins enabled; persistent Epic sign-in; no engine/plugin source or timeout changes; more than 10 GiB Windows commit headroom while the character is loaded; DNS and TCP 443 connectivity to the AutoRig host succeed.
Frequency: 4/4. Reproduced in the initial sign-in session, a second request in that session, a fresh Editor session with persistent sign-in, and another fresh Editor session after changing the network path. The last two controlled requests each failed approximately 5 minutes 26 seconds after submission.
This confirms the direct failure point is remote status polling timeout, but does not prove whether the underlying cause is a backend job, account entitlement, regional routing, or UE 5.8 client/service compatibility. Raw logs are intentionally not attached because they may contain account or client identifiers.
What Type of Bug are you experiencing?
Animation
Steps to Reproduce
- On Windows 11, launch Unreal Engine 5.8 and open a newly created MetaHuman Character asset.
- Enable the MetaHuman Character and MetaHuman Live Link plugins and confirm the Epic account is signed in.
- Confirm more than 10 GiB of Windows commit headroom while the character is loaded.
- Click Create Full Rig once.
- Observe that the request is accepted and reaches 75% / RUNNING.
- Wait for completion.
- After approximately 5 minutes 26 seconds, observe the HTTP 300-second timeout, Server Error, and the character returning to the unbound state.
- Repeat only in a fresh Editor session or after changing the network path; the same failure reproduces.
Expected Result
The AutoRig service should return the completed rig data, the MetaHuman Character should become Full Rig bound, and Unreal Editor should continue without an HTTP timeout or Server Error.
Observed Result
The request is accepted and reaches 75% / RUNNING, but status polling exceeds the 300-second HTTP limit. Unreal Editor reports Server Error, returns the character to the unbound state, and the asset remains unchanged. This reproduced 4 out of 4 times across fresh Editor sessions and a changed network path.
Affects Versions
5.8
Platform(s)
Windows