Choosing the next step

After you identify the likely issue, choose the next action carefully. The wrong action can waste time or create duplicates.

When Retry Is the Right Choice

Use Retry after:

• a connection problem has been fixed
• the analyzer has been synced or corrected
• a missing purchase order has been created
• a temporary timeout or service issue has passed

Retry changes the status back to Pending, clears the old error details, and increases the retry count.

When Review Is the Right Choice

Use Review when:

• the status is Review Required
• extracted values need to be corrected by a user
• the document is readable, but some fields are wrong or uncertain

During review, you can:

• preview the original file
• correct extracted values
• approve the document so creation can continue

When Not to Retry

Do not use Retry as the first reaction when:

• the document is in Review Required
• a Business Central document already exists
• the underlying setup problem has not been fixed yet

If a created document number already exists, open that record first so you do not create duplicates by mistake.

When to Stop and Ask for Help

Stop and involve an admin or support person when:

• the same error returns after the underlying issue was already fixed
• you cannot tell whether a document was already created
• the problem points to connection, analyzer, or setup issues rather than a single document
• the queue or processing log shows a broader pattern instead of one isolated failure

For the exact details to collect before escalating, use Processing logs and support details.