Processing Logs, Job Status, and Job History
The shared processing console distinguishes a queued job from a stalled one and keeps retained outputs together.
Queue and processing
Pending means the request was accepted and is waiting for serverless orchestration or a Fargate worker to start. Processing begins after a worker claims the job, and staged logs then describe the current operation and processed-object counts. Active rows blink until the job completes or fails; completed and failed rows use distinct status colors.
Large source-derived Black layers are processed in six coarse batches. The log records when each batch starts and completes, followed by overlap-validation checkpoints. These updates are intentionally restrained: a batch may take some time, but advancing batch totals show that the worker is still making progress without filling the console with one line per geometry fragment.
Signed-in Job History
Job History is a registered-user feature tied to the account, not the current browser. It lists retained Rasterizer and Fauxlographic Artwork jobs, their terminal or active status, requested processing logs, run details, and available downloads.
Expanded details show start and end time, job type, processing parameters, material, and compact swatches for the official colors actually selected for the job. The stored settings display is a record of the request; it does not add unselected colors to an output.
Guests can follow the one job currently open on the Rasterizer page, but guest jobs are not added to Job History and cannot be recovered from its list after navigating away, refreshing away the task, clearing site data, or losing the guest capability.
Log polling
Logs are loaded only when requested. While an active job is open, the Load Logs control becomes a polling toggle: select it again to stop. Polling also stops and closes that job's accordion after 30 minutes, preventing a browser left on a stuck job from making indefinite status requests. Open the row and load logs again when you want another check.
Secure storage, transmission, and access
Uploaded input assets and generated job files are kept in private object storage configured to block public access and use AES-256 server-side encryption at rest. The site uses HTTPS to encrypt uploads and downloads in transit between the user's browser and the site.
Every queued job is bound either to its signed-in account or to a temporary guest capability. Requests for processing status, logs, and generated output downloads must match that binding. Other users cannot view or download another user's job results, and submitted artwork, Material Library files, and Fauxlographic Palette inputs are not exposed through public download routes.
Your engraving assets remain yours throughout this process: uploading them for processing does not make them available to other users.
Downloads, deletion, and retention
For signed-in jobs, .svg and .lbrn2 download actions become available after successful completion. Account job inputs, outputs, and logs are retained for up to seven days. Delete Job and Assets removes the history record together with that job's retained uploads and generated outputs; saved palettes and Material Libraries are not removed. Download important work promptly rather than treating Job History as permanent storage.
Guest Rasterizer outputs are presented only on the active Rasterizer page. The signed download links shown when completion is observed expire after 15 minutes, and there is no guest Job History from which to recover them. Download every guest output before leaving or refreshing the workflow.
Signed-in users can return from another browser or device for the remainder of the seven-day window. This portable access is one of the practical benefits of membership.