Logfile in AMALYTIX

On the Settings / Logfile page, you can see all important system messages, warnings, and errors at a glance. The logfile is your first point of contact when something in AMALYTIX does not work as expected.

Why the Logfile is Important

Many processes in AMALYTIX run in the background and take some time. It is not always immediately apparent whether a process was successful. If an error occurs, it is automatically recorded in the logfile. Here you can:

  • Understand what happened
  • Identify the cause of a problem
  • Provide information for support

Your logfile in AMALYTIX

Logfile Columns

ColumnDescription
TypeType of entry (Information, Warning, Error)
DateTime of the event
CategoryArea where the event occurred
EventBrief description of the process
MessageDetailed error message or information
MarketAffected marketplace (if product-related)
ASINAffected ASIN (if product-related)

Entry Types

The logfile distinguishes three types of entries:

TypeMeaningExample
InformationNot an error, just a status messageReport was successfully created
WarningNon-critical error, usually no immediate action requiredASIN not found when adding to watchlist
ErrorSerious error, should be checked promptlyProduct detail page on Amazon not accessible

Categories

Entries are divided into the following categories:

  • Product - Events when adding or updating products
  • Snapshot Updates - Events when updating snapshots
  • Reports - Events during report generation
  • Listing Update - Events during content changes
  • Snapshot Translations - Events during automatic translations

Common Problems and Solutions

ASIN Cannot Be Added

Possible causes:

  • The ASIN does not exist on the specified marketplace
  • The product page is temporarily unavailable (404 error)
  • The variant is not available

Solution: Check the ASIN directly on Amazon. If the product exists, try again later.

Product Is Not Updated

Possible causes:

  • Temporary connection issues with Amazon
  • The product has been removed by Amazon

Solution: Check the exact error message in the logfile and contact support if needed.