Before starting generation

1. 01

   Confirm the document type and the information the request must contain.

2. 02

   Verify the project number, name, and essential information in the official project record.

3. 03

   Confirm that the required template or example is available to your organization when that prerequisite applies.

4. 04

   Check recipients, dates, and special parameters before submitting the request.

Processing appears stuck or no document appears

1. 01

   Keep the conversation open and allow a reasonable amount of time for the requested document type.

2. 02

   Open the notification inbox, review unread items, and look for a Document ready notification or an error message.

3. 03

   Compare the project, document type, and time before opening a result.

4. 04

   Refresh the page once if the state does not change.

5. 05

   Avoid submitting the same request repeatedly; duplicate processing can produce several versions that are difficult to distinguish.

6. 06

   If the problem continues, record the time, document type, authorized project, and displayed message before requesting support.

The document is ready, but its content is not suitable

• Do not send the document until errors have been corrected.
• Confirm the project, recipient, template type, dates, amounts, units, and required sections.
• Compare the information with your organization’s original sources and official systems.
• Request a specific correction or restart generation only after correcting the input data.
• Have the final version reviewed and approved under your organization’s process.

Distinguish unavailability from an incident

Feature in preparation

If generation is not yet offered in your environment, a missing command or result is expected and is not a processing failure.

Missing prerequisite

A visible command can remain inactive until the project, template, or required information is complete.

Processing underway

A started request can take time; check its status and notifications before retrying.

Confirmed incident

An error message, explicit failure, or persistent absence of an expected result after checks justifies a report.

Practical guidance

Identify the stage that failed: request validation, processing, delivery link or file content. Confirm the selected document type and required context before retrying. If the file already exists but the notification link fails, diagnose access to that result instead of assuming generation must be repeated.

Advanced tips

Retain the original request, approximate start time and terminal error in an anonymized report. Distinguish a missing required value from an unavailable document type and from an invalid output; each requires a different correction.