Monitoring Version Generation Progress and Results

Opening a version generation job and identifying its current state

In Atloria, start from the Versions area inside your project and open the version you recently generated. If your team also uses a generation queue or job list, you can open the same run from there and then move into the job details view. The job details screen is where you confirm whether generation is still running, has finished, or needs attention before anyone starts editorial review.

At the top of the job details page, look for the status badge in the header. This badge is the quickest way to understand the current state of the run. You may see states such as:

• Queued for a run that has been submitted but has not started yet
• In Progress for a run that is actively moving through processing stages
• Completed for a run that finished and has results ready to inspect
• Needs Another Pass for a run that finished but should be regenerated before review

Below the header, use the summary area to confirm you are looking at the right run. This section typically shows the source item used for generation, the target version, when the run started, when it was last updated, and the current stage. These details are especially useful when several versions are being generated around the same time.

The actions available on the page change with the status. While a run is active, you will usually focus on View Progress or the live status area. Once it finishes, the main action shifts to opening the generated result and checking warnings or notes. If the run is marked Needs Another Pass, look for the action that starts a rerun instead of sending the version forward.

Following progress while generation is running

When a version generation job is running, stay on the job details page and watch the progress area near the top of the screen. Atloria shows progress in a way that helps you tell whether the run is actively moving or waiting at a step. The most useful indicators are the percentage complete, the current stage label, and the animated running state.

As the job advances, the stage label helps you understand what Atloria is doing. Depending on the run, you may see updates that reflect steps such as:

1. Content extraction from the source material
2. Draft generation for the new version output
3. Validation to check the generated content
4. Final assembly to prepare the finished result

These stage names matter because they tell you where the run is spending time. For example, a job that remains in Validation may still be working normally, while a job that has not changed stage or percentage for a long period may need a closer look.

Use the activity feed or status timeline on the same page to follow timestamped updates. This view shows how the run moved from Queued to active processing and then through each stage. It is the best place to confirm that Atloria is still recording progress, even if the percentage changes slowly.

If you are unsure whether the run has advanced, refresh the page or reopen the job details view from the version list. Compare the Last updated time with the current stage. If both remain unchanged after you check again, treat that as a sign to review the run more carefully before waiting longer.

Reviewing generated results when the job finishes

Once the status badge changes to Completed, open the result panel from the finished job. This is where you review what Atloria generated for the target version and decide whether it is ready to move into editorial review. Do not rely on the completed badge alone. A finished run can still include warnings, skipped items, or validation notes that affect release readiness.

Start with the completion details shown near the top of the result view. Confirm the Success or completion status, the Finished timestamp, and any summary information attached to the generated version. This summary helps you verify that the output belongs to the version you expected and that the run ended normally.

Next, compare the generated output with the source content the run used. Focus on whether the expected sections appear, whether the structure looks complete, and whether the generated version reflects the intended source material. If you already worked through release preparation in Creating Release Ready Documentation Versions, use that same release-readiness mindset here without repeating the full preparation process.

Before you hand the version to editors or reviewers, read every warning and note attached to the result. Pay close attention to:

• Warnings that point to incomplete or uncertain output
• Skipped items that were not included in the generated result
• Validation notes that indicate checks passed with concerns or did not fully pass

A completed result is ready for review only when the output looks usable and the attached notes do not block normal editing and approval. If the result summary or warnings suggest missing sections or unreliable output, stop here and plan another pass instead of sending the version forward too early.

Deciding when generated output needs another pass

A version does not need another pass just because it is imperfect. In Atloria, the key question is whether the current output is good enough for editorial review or whether the issues are serious enough to block review entirely. The Needs Another Pass state is your clearest signal, but you should also use the result details to make the decision even when the run shows as completed.

Open the result details and look for the reason Atloria is recommending another pass. Common signs include missing sections in the generated version, low-confidence output, failed checks, or warnings that clearly block review. If the result panel shows that important content was skipped or validation raised concerns that affect the whole version, rerunning is usually the better choice.

Use this distinction when deciding what to do next:

• Issues that can stay in editorial review:

  • Minor wording problems
  • Small structure adjustments
  • Limited clean-up that editors can fix directly

• Issues that should trigger another pass:

  • Major sections missing
  • Validation problems that affect trust in the output
  • Repeated skipped items tied to important content
  • Result notes that explicitly mark the run as incomplete

When you decide to rerun, record the reason in the version’s notes, comments, or team workflow area if your project uses one. Keep the note specific so Documentation Managers and Technical Writers can understand why the first result was not accepted. A short explanation such as “missing setup section in generated output” or “validation warnings blocked review” is more useful than a general note saying the run “looked wrong.”

This makes later comparisons easier and helps your team avoid repeating the same decision discussion on every attempt.

Starting another generation pass and tracking the rerun

If the current output is not ready, start the next attempt from the finished job view. In Atloria, look for an action such as Regenerate or Run another pass on the result screen. Use that action from the version you already reviewed so the rerun stays connected to the same documentation workflow.

After you start the rerun, check how Atloria records it. Depending on how your workspace is set up, you may see either:

The attempt number is especially important when you need to compare results. Make sure you open the latest attempt before reviewing progress or warnings, since older runs may still appear in the history.

Track the rerun exactly the same way you tracked the original job. Watch the status badge, progress percentage, current stage label, and activity timeline. If the first run stalled or produced incomplete output, pay extra attention to whether the rerun moves cleanly through the same stage.

When the rerun finishes, compare the latest result with the previous attempt. Check whether the warnings are gone, whether skipped items were resolved, and whether the generated version now includes the content that was missing before. If the rerun fixed the blocking issues, the version can move forward to review. If not, keep the attempt history visible so your team can see the pattern before deciding on another rerun.

Fixing common issues when progress or results do not look right

Most generation checks in Atloria come down to reading the status badge, the timeline, and the result notes together. When something looks off, use the job details page before deciding whether to wait, review, or rerun.

If a job appears stuck in Queued or In Progress, open the status timeline and check whether new updates are still being added. Then reload the job details page and compare the current stage with the Last updated time. If the timeline has stopped changing and the stage remains the same after refreshing, treat the run as stalled rather than assuming it is still moving normally.

If progress reaches the end but no usable output appears, go straight to the result summary. A finished run may still be blocked by validation notes, warnings, or partial generation. Look for messages that explain whether the output was incomplete, whether some content was skipped, or whether the version was completed with issues.

When another pass produces the same problem, compare the attempt history side by side. Focus on whether each attempt stopped at the same stage or repeated the same warning. Repeated failures at the same point usually mean your team should not keep rerunning without first documenting what is happening for the next reviewer or manager.

If team members are unsure whether to review or rerun, use the final state shown on the job and the notes attached to the result:

• Completed with no blocking warnings usually means the version is ready for review
• Completed with serious warnings means you should inspect the result carefully before sending it on
• Needs Another Pass means rerunning is the safer next step

For broader job handling and result management, see Managing Version Generation Jobs and Results.

Overview

This guide focuses on the point between generation and editorial review: watching a version generation run, confirming whether it is moving normally, and deciding what to do with the result. In Atloria, that work happens on the job details page and the completed result view, where the status badge, progress area, timeline, and result notes tell you whether a version is ready to move forward.

You will usually use this workflow after you have already created the version run. If you need help starting a new run, go back to Generating New Documentation Versions. If you need help comparing outputs after generation, use Comparing Version Output and Release Readiness or Comparing Documentation Versions for Release Decisions.

The main tasks covered here are:

• Opening a generation job from the Versions area or job list
• Reading the current status, progress percentage, and stage label
• Following timestamped updates in the activity feed or timeline
• Reviewing completed output, warnings, skipped items, and validation notes
• Deciding whether the version is review-ready or needs another pass
• Starting a rerun and checking whether the latest attempt fixed earlier issues

This guide does not repeat the full release-readiness process from Creating Release Ready Documentation Versions. Instead, it helps you decide whether the generated output is stable enough to enter that review path at all.

The next document in this workflow is Generating Documentation Versions and Monitoring Results, which brings generation and monitoring into one repeatable working pattern.

Prerequisites

Before you monitor a version generation run in Atloria, make sure you already have access to the project and a version generation job to open. This guide assumes the generation process has already been started and that you are checking progress or reviewing the result afterward.

You should have:

• Access to the relevant project workspace in Atloria
• Permission to open the Versions area and view version records
• At least one version generation run that is Queued, In Progress, Completed, or Needs Another Pass
• Enough familiarity with your team’s version naming so you can identify the correct target version
• The source content or source item context needed to confirm the generated result matches the intended input

It also helps if you already understand the earlier parts of the version workflow:

• How to start a run: Generating New Documentation Versions
• How Atloria tracks job lists and results: Managing Version Generation Jobs and Results
• How to judge release readiness after generation: Creating Release Ready Documentation Versions

If you are opening a rerun, be ready to compare the latest attempt with the previous one. That means knowing which warnings, missing sections, or validation notes caused the earlier result to be rejected.

For teams working together, agree before you begin whether your role is to monitor progress only, decide on reruns, or hand completed versions to editors. That keeps the status badge and result notes from being interpreted differently by different reviewers.