What happens after a profile run starts

How a profile enters the queue, how demo and full runs differ, and where to check statuses, credits, logs and the result.

What happens after a profile run starts — Eofferix
Eofferix interface screenshot: What happens after a profile run starts

After you start a profile, Eofferix goes through preparation, queueing, processing, result storage and optional external delivery.

Demo run and full run

A demo run checks the template on a limited sample. Use it to inspect the output structure and catch errors before processing the entire source. A full run processes the whole source, spends credits according to actual work and creates the production result.

Queue and statuses

  • Queued means the job is waiting for processing to start.
  • Running means the service is reading the source and applying rules.
  • Done means the result is stored and can be downloaded or delivered.
  • Error means the run stopped; the reason is in the logs.

Credits, history and logs

Before a full run, the service estimates the amount of work. After completion, run history shows start time, final status, duration and result location. Logs help diagnose mapping, source and transformation problems.