SDX-Cloud: Processing jobs

TL;DR: Processing jobs lists everything that SDX-Cloud runs in the background, such as a data model import or a point cloud export, newest first. Filter by text, status, and person, then open a job to see when it was queued, how long it ran, and why it failed. The lists are read-only.

What a processing job is

A processing job is work that SDX-Cloud runs in the background after you start it, for example processing a data model, creating an orthophoto, or calculating a stockpile. While a job runs, you can keep working in SDX-Cloud.

Where to find processing jobs

Other ways in

• Activity center: Select the activity center button next to Search at the top, then the Processing jobs tab. It shows your latest jobs. Show all jobs opens the full list in your user settings. See SDX-Cloud: Activity center.
• Data model status: On the Data page of a project, select the status of a data model, for example Failed. A Processing jobs panel opens with the jobs of that data model only.

How the list is organized

Jobs are grouped by day, newest first. Each day heading shows the date (today is marked TODAY) and the number of jobs on that day. Scroll down to see older days.

Each job in the list shows:

• Start time of the job, on the left.
• A colored dot: green for a finished job, red for a failed job.
• Job type, for example Data model processing, followed by the name of the item it worked on when there is one, for example the data model or stockpile.
• Person who started the job. Project and organization lists show it; your own list does not.
• Error message in red, when the job failed.
• Processing time on the right, for example 1m 8s.

Job types

The job type says what the job did. Examples:

• Data model processing, Data model deletion
• Point cloud creation, Point cloud cleaning
• Orthophoto creation
• Reference model processing
• Apply manipulations, Manipulation processing, Manipulation deletion
• Stockpile calculation, Stockpile recalculation, Stockpile deletion
• Measurements export
• Photogrammetry upload, Photogrammetry import, Image archive import, PocketScan import

Filter the list

The filters sit above the list. They work together: a job must match all of them.

• Filter (text field): type a word to keep jobs whose job type, item name, person, or error message contains it, for example Stockpile or coordinate.
• Status filters: select one or more of Created, Queued, In progress, Finished, and Errored. A selected status turns blue. With two statuses selected, the list shows jobs in either status. Created, Queued, and In progress show jobs that have not ended yet. Errored shows the jobs that failed.
• People (project and organization lists only): opens a list of the people who started jobs, with a search field. Select one or more people. The button then shows how many are selected, for example People: 1. Reset in that list clears the selection.
• Clear filters: appears as soon as a filter is set and removes all of them.

When no job matches, the list says No processing jobs match your search.

Open a job

Select a job in the list to open its details. The arrow at the top left returns to the list. The details have these parts.

Times

Error

A failed job shows a red box with an error code and a message. A known problem has a message that names the cause, for example The coordinate system of the project and the point cloud do not match. An unexpected problem shows An unexpected internal error occurred. In that case, contact Sodex support and include the Job ID.

A data model that lies more than 130 km from the project origin fails with the error MODEL_TOO_FAR_AWAY_FROM_PROJECT_ORIGIN. The project origin is set by the first processed 3D data or the first use of the SDX-PocketScan Pole, and the first page of the project settings shows it. SDX-Cloud enforces this limit to keep a precision of 1 cm across all data models in a project. If the origin is wrong, ask Sodex support to change it. If the data does not belong in the project, create a new project for it. The new project gets its own origin.

Context

• Status: for example Finished or Failed.
• Triggered by: the person who started the job, or You. Not shown in your own list.
• Project: the project the job belongs to. The button next to it opens the project.
• Last update: when the job last changed.
• Job ID, Project ID, User ID: each has a copy button, so you can paste the ID into a support request.

Parameters

The item the job worked on, for example the Data model or Stockpile, with its ID.

Timeline

Each stage of the job with its date and time, and how long the job stayed in that stage: Created, Ready for pickup, Processing, Worker finished, Post-processing, and at the end Finished or Failed.

Logs

The messages the job wrote while it ran. The number next to Logs is the number of entries. Each entry shows the date and time, its level, the part of the processing that wrote it, and the message.

The level buttons above the entries show or hide one level each: Info, Warning, Error, and Critical. A job shows only the levels it actually wrote. Verbose is off at first; turn it on to also see the detailed step-by-step entries. For a failed job, hide Info to keep only the warnings and errors.

In the error box of a failed job, Traceback shows the technical detail of the error below the message. Include it in a support request if Sodex support asks for it.

What the lists do not do

The lists show which jobs are waiting or running and how many there are. They do not show how long a job will still take, its place in the queue, or its progress.

You cannot cancel, retry, or change a job from these lists. Job history is kept without a time limit.

Related articles

• SDX-Cloud: Activity center
• SDX-Cloud: User settings