Pending imports
An import can be queued for a project from outside the editor, for example from the Prophouse web library. Queued imports wait on the server until an editor with that project open runs them. The Prophouse panel (Window → Prophouse) lists them under Pending imports.
How imports find your project
Section titled “How imports find your project”Every import targets a project key. The editor uses the Project Key (blank = .uproject name) setting, which defaults to the name of your .uproject file. The key is shown in the Prophouse panel header next to the connection status. When you queue an import from the web library, pick the same project name.
If several teammates open the same project, they share its key, and any of them can run an import queued for it. The server makes sure only one editor claims each import.
Run a queued import
Section titled “Run a queued import”-
Open Window → Prophouse.
-
Under Pending imports, find the job. Each row shows
#<id> <status> N entries / N objects / <size>, and below it the destination root and when it was last updated. -
Click Import on a row with the status
queued. -
Follow progress under Activity:
Claiming job...,Fetching closure manifest...,Scanning for local modifications...,Downloading blobs...,Assembling packages...,Reporting to server.... -
Answer the conflict dialog if it appears. See Resolve conflicts.
Click Cancel next to the Activity status to stop an import before its assets are placed. The job is marked failed and nothing is placed (Pull cancelled - nothing was placed.). Only one import runs at a time.
Imports place assets the same way as the Prophouse Browser: under the job’s destination root, in per-class folders, with every reference rewired. See Where assets land.
Reports
Section titled “Reports”When an import finishes, Activity shows a heading like Pull results - 14 added, 2 skipped, 1 conflicts, 0 failed and one row per asset:
| Section | Meaning |
|---|---|
added |
Placed in the project, as a new asset or a safe replacement of an unmodified older version. |
skipped |
Already present and identical. |
conflict |
Modified locally; the row says how it was resolved. |
failed |
Could not be placed; the row includes the error. |
The report is also sent to the server, where the web library shows it on the job. The list keeps finished jobs too; click View report on any job the server has a report for.
If a job contains assets saved by a newer engine than yours, Import is blocked and Activity lists the offending assets. See Engine version checks.
Polling and refreshing
Section titled “Polling and refreshing”While Enable background polling is on (the default), the editor checks the server for queued imports every Poll Interval Seconds (default 60, minimum 10). Polling never runs an import by itself: you still click Import.
To check right away, click the refresh button (circular arrows) next to Pending imports. It asks the server for new imports, refreshes the list and re-checks the connection. The button works even when background polling is off; in that case the panel shows Background polling is disabled — refresh manually with the arrows next to Pending imports.