#761

Two tabs that people look at when something has gone wrong: «Log» — what the program did, «Issues» — what it failed to do.

The «Log» tab

A line-by-line chronicle of the work: the connection to the server, the response, how many orders are to be downloaded, the downloading of each archive, the unpacking, the conversion, the copying into the machine folders. The lines are coloured: green — success, orange — a warning, red — an error, blue — downloading.

  • Clear — clears only the display in the window; the log file stays.
  • Copy — the whole text to the clipboard. This is the most convenient way to send the log to support.
  • Open the log file — opens 1.log. In it the new entries are at the top, so there is no need to scroll down.

The log window shows only the current work session: after the program restarts it is empty, while the file is not. If the log has scrolled up because you were looking through it, new lines will not jump — scroll down.

The «Issues» tab

Only one thing gets here: the files and folders the program tried to delete and could not. That happens when the server has withdrawn an order or you deleted it by hand while the file was busy at that moment.

The columns: order, path to the file, reason, date and error text. Typical reasons:

  • No rights / file busy — the file is open in another program or in Explorer. Close it and repeat.
  • The folder is not empty — inside there is something the program did not put there. Look at it yourself and remove it by hand.
  • File not found — it has already been deleted earlier. Such an entry can simply be marked as resolved.
  • Partially — some of the order files were deleted, some were not.

Buttons

  • Refresh — re-read the list.
  • Retry deletion — try once more. If it worked, the entry leaves the list.
  • Mark as resolved and Mark all as resolved — remove the entries from the list. This means exactly «I am aware, stop showing it»: the file itself stays on the disk.

When the list is empty

An empty «Issues» tab is a normal state. If entries pile up regularly and always for the same folder — most likely another program on this computer is holding it open.

Errors of the exchange with the accounting system are not looked for here

Failed records from BAS / 1C do not get here — the exchange has its own places:

Such operations are visible in the program log as well — they make it easy to understand whether a record reached the server.