You were charged, the job finished anyway, and the image is waiting for you at uni.xyz/unify/jobs. Credits are taken the moment you press Generate, not when the picture appears, so leaving the page costs you the wait rather than the result. Do not press Generate a second time: that queues a new job and takes a second payment for work you have already paid for.
The page watches the job, it does not run it
Pressing Generate hands the work to a queue on the server. The page then asks the server every three seconds whether that job has finished, and paints the result when it has. The asking belongs to the page. Navigate to another part of UNI, reload, or close the tab, and it stops. The job in the queue never notices and finishes normally.
Switching to a different browser tab is not the same thing and is safe. The page is still open, the checking continues, and the result is on screen when you come back.
The Render page has no memory of a job in flight
Come back to Render, Stage, Upscale or Edit and you get an empty page. There is no banner saying something is still running, and no way to reattach to the run you started. This is the expensive part, because the natural response is to upload the same image again and press Generate.
Where the finished image is
Two pages hold it:
- Jobs, at uni.xyz/unify/jobs, lists every job you have run, newest first, with its status. Open one to see the input, the result, and Download Full Resolution. Failed jobs are listed too, with the error the server recorded against them.
- Assets, at uni.xyz/unify/assets, shows finished images only, as a grid, with a download on each.
Both pages keep checking on their own while a job of yours is still running. So you can start a render, move straight to Jobs, and watch it land there instead of holding the Render page open.
A failure now gives the credits back, with one gap
If a queued job fails, render, upscale and edit now refund the credits automatically, the same as video always has. The gap is earlier than that: the charge happens before your image reaches storage, and if that upload itself fails, there is no job row for the refund logic to act on, so those credits are not returned automatically. If a render, upscale or edit failed and you were not refunded, ask the UNI team for the credits back and say what you were generating and roughly when.
Chat behaves differently
A render you ask the UNIfy agent for in chat draws on the free daily allowance first, and a failed one gives its free slot back rather than consuming it. If the allowance was already spent and that render was paid for in credits, those credits are not returned either.