Skip to content
  • There are no suggestions because the search field is empty.

How to Troubleshoot Amazon Settlement Report Errors in Automated Workflows with Webgility Desktop

This article helps Webgility Desktop users in addressing issues encountered when downloading or posting Amazon settlement reports, especially within automated workflow environments. It guides users through identifying report-related errors and provides step-by-step troubleshooting to resolve common automation process failures, ensuring smooth and reliable Amazon settlement reporting.

Overview

This article guides you through addressing issues that you may encounter when downloading or posting settlement reports, particularly in automated workflow environments. It covers identifying report-related errors and step-by-step troubleshooting for common automation process failures.

Prerequisites

  • Access to the account or reporting dashboard( Webgility and QuickBooks).
  • Familiarity with the automation process for settlement report generation and posting.
  • Access to relevant system logs or error messages.

Identifying the Issue

Before proceeding, clarify:

  • Is the download of the settlement report failing, or is posting the report the problem?
  • Is the issue reproducible manually, or only in automated workflows?
  • Are there any specific error messages displayed during download or posting?

Collect:

  • The exact error or a screenshot, if possible.
  • The steps leading up to the failure.

Troubleshooting Steps

1. Verify Report Availability

  • Navigate to the Settlement Reports section in Webgility.
  • Ensure the report is generated and available for download.

2. Manual Download Verification

  • Attempt to Download the relevant settlement report.
  • Confirm whether the file is received without error.
  • If the download fails:
    • Check for browser issues, pop-up blockers, or file permission settings.
    • Try a different browser or clear the cache.

3. Automation Workflow Inspection

  • Review the automation process steps (e.g., scheduled report download settings, posting mechanisms).
  • Check if:
    • The automation runs at correct intervals.
    • The script/service account has the necessary permissions.
    • File paths and credentials are up to date.

4. Error Message Analysis

  • Analyze specific error messages from the workflow or user interface.
  • Common causes may include:
    • Missing reports.
    • Incorrect file format.
    • Timeout during file transfer.
    • Authentication failure.

5. Attempt Manual Posting

  • Try to manually post the downloaded report using the Post button.
  • If successful, focus troubleshooting on automation or permissions.

6. Review System Logs

  • Check scheduler logs for detailed error output.
  • Look for:
    • Authentication errors.
    • Network connectivity issues.
    • Report file corruption or mismatches.

7. Guide User for Successful Completion

  • Once the root cause is determined, go through resolution steps:
    • Update credentials or permissions as needed.
    • Fix automation script paths.
    • Adjust browser or environment settings.