The Job Queue

Every conversion, deduplication, cleaning run and comparison in DataTray runs as a job in the background, so you can keep using other utilities — or close the window to the tray — while work continues.

Open the Job Queue from the System section of the sidebar. It has two lists:

• Active — jobs that are queued or currently running, each with a live progress bar and a status message. Empty, it reads "No jobs running. Start one from a utility."
• Recent — jobs that have finished, failed, or been cancelled. Use Clear finished to tidy the list. Your recent history is remembered across restarts.

Job statuses

Per-job actions

Depending on a job's status you will see buttons to:

• Cancel — stop a queued or running job.
• Retry — run a failed or cancelled job again.
• Open — open the finished file in its default app.
• Reveal — show the finished file in File Explorer.
• Copy log — copy the job's log to your clipboard (useful when reporting a problem).
• Remove — delete a finished job from the list. This does not delete the output file.
• Log — expand to read the job's step-by-step log and any error detail.

Running several jobs at once

DataTray runs multiple jobs simultaneously, up to the Job concurrency setting in Settings. Extra jobs wait in the queue and start automatically as slots free up.

Note that the tiles queue differently. Dedupe & Merge, Clean & Anonymize and Compare Files put one source file into one job. Data Converter depends on what you asked for: converting forty files is forty jobs, combining forty files into one is a single job, and splitting one file into many is a single job that writes many parts.

Data Explorer is not a job tile. Browsing rows, profiling and running SQL all happen live in the panel and never appear in the queue. Only its Export and Report buttons enqueue a job.

Data work is genuinely CPU- and disk-heavy. If your machine feels sluggish during a large run, lower Job concurrency rather than assuming something has hung.

If something goes wrong here

• A job says Failed. Expand its Log and read the error — it names the file and the reason. Copy log if you want to keep the detail, then fix the cause and press Retry.
• Jobs are queued but nothing is starting. Every slot is busy. Raise Job concurrency in Settings, or wait for the running jobs to finish.