Tasks

What a task is

Tasks are background jobs that turn provider downloads or uploads into project assets, process models, and perform other queued preparation. You can leave the page while a task runs. Its progress remains available from Tasks and the header notification center.

A queued task is waiting for capacity. Running is active work. Retrying means an automatic or requested retry is pending. Completed means the result is ready. Failed means the latest attempt ended with an error. Archived hides finished history from the default active view; it does not undo the produced asset.

Find the task you need

In the Web UI, choose Resources in the sidebar, then Tasks at /resources/tasks. Tasks, Exports, Assets, and Uploads share compact cards and a header containing search, Sort, Filters, and Refresh. Search remains selected when switching tabs; the project filter applies to Tasks, Exports, and Assets. Filters are specific to each tab; Tasks includes Project, Type, Status, and History, with active history as the default. Sort offers newest, oldest, and name. Results are paged, with more cards per page on wider and taller screens. On narrow screens the toolbar and long tab labels wrap, and cards form a single column without horizontal scrolling. Retry is in each eligible failed task card’s More actions menu.

Click the active-job number beside Resources to open Active work, then View tasks to show all queued, running, and retrying tasks in the selected workspace. This opens /resources/tasks?status=in-progress and clears previous search and project filters. The In progress control above the cards removes that status filter, and Filters → Status also offers In progress. Reloading or reopening the same link retains the selected status. The Tasks and Exports tab counts cover the entire selected workspace, including jobs outside the current search or filters. Zero is muted; a dash means the count is not yet available. Project backups are listed and counted in Exports.

Check the active team before searching. A task belongs to the team that owns the project or model, so it will not appear under another selected team.

Inspect task details

Click a task card to open its details. The summary shows the project when applicable, creation and update times, priority, retry count, archive state, requested and current provider, and usage. Flags explain special choices such as upload mode or fallback.

In the Web UI, active task details refresh automatically. Use Overview for progress and the result, Activity for timestamps, logs and the full error, and Technical for provider choices and output measurements. Progress follows the stages needed for that task: terrain, vectors, imagery, project archives and model previews have different steps. Stage progress is not an estimate of time remaining. Activity logs include elapsed time and memory measurements for important processing operations. Temporary connection interruptions can retry automatically; wait for the task to finish or fail before starting another attempt. Download appears for available completed task output. Retry and archive actions are in More actions; archiving a normal task preserves its produced data, while archiving a backup removes the backup file. Output is also accessible from the project or Assets. On failure, read the final error and the last useful log lines before retrying; they usually identify credentials, provider coverage, input format, available capacity, or processing failure.

Stop, archive, retry, and use bulk actions

Select one or more queued, running, or retrying tasks and choose Stop and archive when the work is no longer wanted. Stopping ends the job and removes it from the active list after the state is saved.

Select completed or failed tasks and choose Archive to clean up the active list without deleting their project results. Select a failed task and choose Retry after correcting the cause. A retry consumes capacity again and may select another available provider when the task allows it.

Bulk actions apply to every selected row that supports the action. Clear the selection and filter by status first if the list mixes jobs you intend to keep and jobs you intend to stop.

Task units and waiting work

A task uses one or more Task Units from the tier capacity. Each used Unit returns after that tier’s rolling replenish interval shown on Usage, so finishing a task does not always make the Unit immediately available. Some optional extensions can add capacity. When a team is over its storage limit, its active tier may make that return take longer or block new work until storage is freed.

A task can also wait because no compatible processing capacity is available, the chosen provider is temporarily unavailable, required credentials are missing, or the team reached another operational limit. Open the task details first, then check Data Providers and Usage according to the message shown.