↑↓ selectEnter openEsc close

    1. Elbuz

    Who did this: the operation log and what a deletion leaves behind

    27 min readUpdated

    Elbuz logs every change and deletion with its time and author: who changed a price, who deleted a product. The document and contact trash bring deleted records back.

    When you need this:

    • Products vanished, nobody admits it — the “Bulk delete” row shows who deleted how many, and when.
    • A price changed — “Operation history” shows old and new values; “Restore” brings back the old one.
    • A manager deleted the wrong order — the document trash restores the whole batch with items for 30 days.
    • Supplier deleted by mistake — the contact trash keeps the card for 60 days.

    Where to start: Account → Operation log, filter by date.

    What the log can do

    Which log to open: five that are easy to confuse

    The word “log” means five different things in Elbuz. Mixing them up costs time: someone looks for a deleted product in the price list log, doesn't find it, and concludes that the system kept no record.

    Where to look for what
    LogWhat it coversWhere it opens
    “Operation log”what the system and people did: every step of every operation, with the time, author, and status“Account” → “Operation log”
    “Operation history”which field values changed: the old value next to the new onethe clock icon in an operation log row
    Trashthe deleted records themselves that can still be restoredthe document list and the contact list
    Price list logfigures for each import from one sourcethe “Log” tab in the source card
    “Deleted products log”rows that ignore rules dropped from the price list during import — it has nothing to do with deleting data from the catalog“Ignore rules” → “Deleted products log”

    The last two are outside the scope of this article. The price list log counts price list rows, not people's actions, and has its own article — what the supplier sent this time. This article covers the first three.

    The name “Deleted products log” matches the question “who deleted the product” almost word for word, so people go there first. It is about something else: it lists the items that ignore rules kept out of the catalog when importing a price list.

    It is kept only if logging such rows is turned on in the source itself, and each new import erases the previous list and writes its own — so the content always looks fresh, even though it has nothing to do with the products you deleted.

    The log also tells you about automation, but from the result side. Why the nightly run didn't start — see the schedule didn't run. Why an automatic rule sent an email or stayed silent — see automatic rules. Both articles explain which log rows to look for in their area.

    How to read the log: two views

    Above the grid there are two toggles: “All records” and “Summary”. The difference is what counts as a row.

    In “All records” view, a row is a single step. A price list import with thirty steps produces thirty rows: “reading file”, “parsing columns”, “applying markup”, and so on. This is the most detailed view and the longest list.

    In “Summary” view, a row is a whole operation, and a “Steps” column appears. The number in it is clickable when there are two or more steps: clicking it opens those steps in a flat list, and a back chip with the tooltip “Back to the operations list” appears at the top. Clicking anywhere else in the row does the same.

    In exchange, “Summary” hides the “Operation subtype” column — the very one you use to find deletions — so to look for a specific action, stay in “All records”.

    Operation log window in All records mode, scrolled right to show User, Status, Level and Object ID columns
    1All records / Summary chips
    2User column
    3Level pill
    4Restore (history) icon
    1. The chips switch between the full list (All records) and one row per operation (Summary).
    2. User — who performed the operation; empty for system rows.
    3. Level — the severity pill: Info, Debug, Warn or Error.
    4. The clock icon opens the change history of the product, document or category.

    The grid has thirteen columns: “Operation type”, “Operation subtype”, “Steps” (only in “Summary”), “Source”, “Info”, “Date”, “Running time”, “User”, “Status”, “Level”, “Cost”, , and a last narrow one with a clock icon. “Cost” is non-zero only for AI operations; all other rows show zero there.

    Two columns don't mean what they seem to. “Source” isn't “where the record came from” — it's the name of what was being worked on: a price list, template, or product name. It is recorded at the moment of the event, so the log doesn't follow later renames: old rows keep the old name.

    “Running time” is filled in not by the step itself but by the step after it — so the last step of an operation usually has this cell empty (some subsystems fill it in themselves).

    Operation log in Summary mode with the Steps column
    1Summary chip
    2Steps count
    3Status column
    1. Summary mode is active: one row per operation.
    2. Steps — number of log entries inside the operation; values above one are links.
    3. Status shows Finished or Error for the whole operation.

    The text in the “Info” column is stored in the language of the person who started the operation. If an import was run from a Ukrainian-language session, the row stays in Ukrainian — even when you view the log in English. Text that has already been recorded can't be translated; operations started in English will be logged in English.

    Severity levels

    The “Level” column shows a badge with one of four values: “Debug”, “Info”, “Warning”, “Error”. Its filter is a drop-down list, so you don't need to type anything.

    “Debug” rows are hidden by default — otherwise service steps would flood the list. To see them, select debug in the “Level” column filter. In “Summary” view they are always counted: the number in the “Steps” column includes them, so it can be larger than the number of rows in the flat list.

    An asterisk after the level label means the row has additional operation data saved — hover over the badge to see it in a tooltip.

    How to find out who did it

    The order that saves the most time: narrow down by date first, then by operation type, and only then read the rows.

    Data has changed: what to do, step by step

    Operation log filtered by User = support
    1User filter with value
    2Clear filter button
    3Refresh button
    1. Typing support in the User filter cell narrows the grid to that user.
    2. The funnel button clears all filters.
    3. The refresh button reloads the grid.

    Almost every column has a filter, and it matches by “contains”: part of a word is enough. The “Operation type” and “Operation subtype” columns accept the label in your interface language — the same one you see in the cell, if the cell has one. The funnel button in the toolbar clears all filters at once (tooltip “Clear filter”), and the one next to it reloads the list (“Refresh”).

    Some operations don't have a label yet, and the cell shows a code instead, for example smart_search. The filter finds such rows too, but you have to type the code itself — in full, exactly as it appears in the cell. The filter first searches the labels, and only when none of them match does it treat your input as a code.

    An empty cell in the “User” column is not a glitch and doesn't mean “the system didn't record it”. It marks rows that weren't written by a person: a scheduled nightly run, a request from an external system, a background job. On the demo account, such rows make up a fifth of the log. There's no point in looking for a specific employee behind them — nobody was there.

    The “Status” column shows “Finished” or “Error” in both views. The filter accepts these words (as well as ok and error), but matches them against the start of the label: “Err” finds errors, but “rror” doesn't. Type the word from its first letter.

    The “Export to file” item in the “Additional operations” menu downloads the log as an Excel spreadsheet. The export respects the grid filters: the file contains what you've filtered on screen. To export the whole log, clear the filters with the funnel button first.

    The same menu has “Stop all operations”: a single command that stops everything currently running in the background. The job queue is cleared completely — unfinished price list imports, , and batch processing are interrupted, and you can't resume them: anything you still need has to be started again.

    That's why Elbuz asks for confirmation first. If only one price list is stuck and the rest shouldn't be stopped, click “Stop import” in that price list's row in the “Price lists” window.

    How long each log is kept

    None of these periods can be changed in the settings — they are built into Elbuz. But they aren't the same for every account: some rows are shortened by the work itself, and the details are below.

    Retention periods
    What is storedHow long
    “Operation log” rows, including everything shown in “Summary” view14 days
    “Organizer: changes” rows — the edit history of organizer recordsas long as the organizer record itself exists
    site parsing rows3 days, and rows for one source are erased even sooner — when the next run for that source starts
    operation cards in the “Run history” window (from a template card)90 days, but the window opens showing the last 30
    “Operation history” — old field values7 days
    document trash30 days
    contact trash60 days
    price list import logthe last 200 runs per source
    Дані таблицею
    ПоказникSite parsing, daily parserSite parsing“Operation history” — old field valuesOperation logDocument trashContact trash“Run history” cards
    Days kept13714306090
    How long each log is kept. The order isn't intuitive: the operation log itself disappears before the trash does, and “Run history” cards outlive everything else, ninety times longer than daily parser rows.

    Work out your retention period in advance, because it may be shorter than it seems. Fourteen days is the maximum for most rows, but site parsing rows are kept for less: three days at most, and when a new run starts for the same source, its previous rows are erased right away.

    If a runs daily, the log keeps rows only from its latest run, while rows of other types sit in the same grid for two weeks.

    You can check your period in a minute: open the log, clear all filters, and scroll to the very bottom — the date of the last row is how far back the log goes. If the event you need is older than that date, there's nowhere left to look.

    Seven days of change history is shorter than a typical vacation. A mistake made on Monday and noticed two weeks later can no longer be traced: by then the old field value is gone, and only an “Update” row remains in the operation log — and even that lasts only fourteen days. If a figure matters, write it down right away, not when you get around to it.

    One detail sometimes works in your favor. Cleanup of old rows doesn't run on its own timer: it runs along the way, together with a price list import, base catalog update, import, export, or parsing.

    On an account where something is imported every day, the periods are kept exactly. On an account where nothing has run for months, old rows may stay longer — but don't count on it: the very first import will clear out everything extra in one go.

    “Summary” view has no retention period of its own: it builds operations on the fly from the same log rows, so it disappears together with them — after exactly 14 days, not after a quarter.

    The ninety days apply to operation cards, and you view them not here but in the “Run history” window, which opens from an export or import template card. It's the only place where you can see the rest of the quarter; even so, the window opens showing the last 30 days each time.

    What a deletion leaves behind

    Here's the main inconvenient truth: what a deletion leaves behind depends on what was deleted. Elbuz has no separate deletion log — deletion records live in the same “Operation log”, and not all of them get there.

    Three different outcomes for a deleted record: the trash restores it, the log tells you about it, and some deletions leave nothing at all
    DocumentContactProducts · category · pricelisttemplate · companystructure nodemanufacturers in bulkSingle manufacturerattribute · photo ·warehouseSomeone deleted a recordWhat kind of record is it?Document trash30 daysContact trash60 daysRow in the “Operation log”14 daysNothingThe record can be restoredwith all its linksYou can see who and when.No way to restoreYou can't even seethat the record existed
    • Action or result
    • Decision: the path depends on the answer
    What leaves a row in the log and what doesn't
    What was deletedRow in the “Operation log”What you can see
    Documentnothe document itself stays in the trash for 30 days, along with the author and date
    Contact, deleted from its own windownothe card stays in the trash for 60 days; the “Moved to trash” event is shown in the card's own history
    Products deleted in bulk from the gridyessubtype “Bulk delete”, the “Info” field shows how many. There's no list of names
    Product deleted individuallyyessubtype “Delete”, the “Info” field shows “Products deleted” and the count, the author, and the time
    Categoryyesa separate row for each, with the category name
    Price list (source)yesthe source name in the “Source” column
    Supplier deleted from the price lists windowyesonly the contact ID, the date, and the author — the row has no name
    Export or import templateyesoperation type “Export” or “Import”, subtype “Delete”
    Company structure nodeyesthe node title
    Manufacturers — via “Delete all manufacturers” or “Delete manufacturers that are not in the base catalog”yestype “Manufacturer”, subtype “Bulk delete”, the “Info” field shows “All manufacturers deleted” or “Manufacturers without products in the base catalog deleted” with the count
    Manufacturer deleted individually, attribute, product photo, warehousenonothing

    To be clear about one thing: not every deletion leaves a trace in the log. Documents and contacts aren't written here at all. So for them, the question “who deleted it” should go to the trash, not the log — and quickly.

    The last line of defense is the nightly database backup. Every night a copy of your entire database is made, and seven copies are kept — roughly a week. You can restore a backup yourself: “Account” → “System settings” → in the left column, the “Other settings” section → the “Restore DB backup” tile; the window lists backups by date, each with a “Restore DB” button.

    Don't rely on it as an “undo” button, for two reasons:

    • the backup contains only the database — uploaded files and photos aren't in it, so photos can't be recovered at all;
    • the whole database is restored, so along with the lost product, all work done after that night is rolled back too.

    So a backup is a last resort for a major loss, not a way to restore a single record.

    One more thing worth knowing in advance: doesn't mean the same thing in different windows. The trash can icon in a grid row is just a delete button, with no storage behind it.

    What exactly changed in a record

    When the record is still there but a value in it is different, the operation log says “Update” — and stops there. What exactly changed is shown in a separate window, “Operation history”.

    In the “Account” menu, a few lines below “Operation log”, there's a “Changelog” item. It has nothing to do with field values — it lists what has changed in Elbuz itself in recent versions. The window you need is called “Operation history”, and it has no menu item of its own at all.

    You open it from the same log — with the clock icon at the end of a row. The icon appears not in every row, but only where the operation concerns a product or document.

    The second way in is the document card: the “Operations log” item in the menu under the three-dot button, and the “Detailed information” button in the header of the “History” block. Both open the same window, narrowed down to that document; the window's title will then say “Detailed information” instead of “Operation history” — it's the same window.

    Transaction history window for a product with the changed price shown as old (red) and new (green) values
    1Old and new field value
    2Restored at column
    3Restore icon
    1. The expanded table lists the changed field: old value in red, new value in green.
    2. Restored at — when the change was rolled back; zeros mean it has not been restored.
    3. The clock icon restores the previous values (not clicked).

    The columns are: “Operation type”, “Source”, “Date”, “User”, then “Restored at” and “Restored by” — these are about a rollback, if there was one — and the record ID. The first row expands on its own: under it is a table of changed fields, with the old value in red and the new one in green. A field that has no new value is labeled “Empty”.

    Only the product header and the document header are recorded here: price, name, description, statuses, dates. Photos, attributes, options, product categories, and document items don't go into the history — they are separate tables, and changes to them aren't shown here.

    And it's recorded only when a person changed the value: saved the product card, edited a cell directly in the grid, set a value in bulk for selected products, or saved a document. After a bulk set, a “before → after” record appears for each selected product whose value actually changed, and “Restore” brings back its old value.

    This applies to the fields of the product card itself and to simply writing a value, including a price in “Fixed” mode. Descriptions and attributes aren't recorded here after a bulk edit — you roll them back through “Recent actions”. Recalculating the price with the “+/−”, “%”, and “*” modes for each selected product isn't recorded here and can't be rolled back through “Recent actions”.

    A price overwritten by the nightly price list import or a base catalog update doesn't get here — and that's exactly how prices change most often in Elbuz. So an empty history window doesn't mean nobody touched the price: it means nobody changed it manually. To see how such a price moved, check the product price history, and look for the nightly run itself in the “Operation log”.

    The “Restore” button

    The last column of every row has an icon with the tooltip “Restore”. It returns the fields to the values they had before the edit.

    Before rolling back, Elbuz asks: “Restore the previous field values of this product? This cannot be undone.” The current values aren't saved anywhere — there's no way to undo the rollback itself, so confirm only when you're sure.

    It has two limitations.

    • It works only for products. For a document, the button is shown but does nothing.
    • It restores only the card fields. It doesn't touch photos, attributes, categories, or links, and you may need to refresh the catalog grid manually after the rollback.

    When the rollback succeeds, you see “Updated”. If instead you see a red “Restore failed”, the fields weren't touched: the record is gone, the product was deleted in the meantime, or the fields already have the values they had before the edit.

    How to restore deleted items from the trash

    The log tells you what happened; the trash gives it back. Elbuz has two trash folders, and both work silently — nothing reminds you about them until you look.

    Document trash

    Right after a deletion, a “Documents deleted: N” message pops up at the bottom with an “Undo” button — the fastest way to change your mind. If you missed it, open the menu in the document list header and select “Document trash”.

    Document trash window with one deleted batch
    1Deleted batch row
    2Undo button
    1. Each row is one deleted batch with date, author and number of documents.
    2. Undo returns the batch to the document list (not clicked).

    The trash shows the 30 most recent batches: each row shows what was deleted, when, by whom, and how many documents. One click of “Delete” in the list is one batch, so it's restored as a batch too. A full snapshot of the document is kept: header, items, links. The retention period is 30 days, and an empty trash says so: “Trash is empty - no documents deleted in the last 30 days”.

    A posted document never gets into the trash for a simple reason: you can't delete it at all until it's unposted. This is a deliberate safeguard — the stock movement and money have already been accounted for.

    What happens to a document after “Delete”: from the trash it either comes back with the “Undo” button or is erased — the trash has no timer of its own, and old batches are cleared by the next document deletion
    posted — deletion won'tworkDeleteUndoolder than 30 daysand another document isdeletedDocument in the listIn the document trashErased for good
    • Start
    • State
    • End

    Contact trash

    In the left panel of the contact list there's a “Deleted” section with a “Trash” item. A deleted contact doesn't go anywhere — it's just hidden from the list, and all its documents, price lists, and history stay in place. The “Restore” button brings the card back, and a “Restored from trash” event appears in its history.

    Contacts window left panel with the Deleted section and the Trash item
    1Deleted section
    2Trash item
    1. Deleted — the left-panel section for removed records.
    2. Trash — opens deleted contacts.

    The retention period is 60 days, as the window states directly: “Deleted records are kept for 60 days, then erased automatically.” Next to it is the “Delete permanently” button with the confirmation “The records and all their links will be erased for good. Selected:” — after that, nothing can help.

    You can't delete your own company at all: Elbuz skips it. For more on the contact card and its event history, see the article on the contact card.

    There are three ways out of the contact trash: back to the list, erased manually, or erased after 60 days. Only the first brings the record back
    your own company — can'tbe deletedDeleteRestoreDelete permanently60 days have passedContact in the listIn the contact trashErased with all links
    • Start
    • State
    • End
    “Document trash” in the list menu: a deletion batch comes back with a single “Undo” — the document is back in the list with its items

    Scenarios

    Some products disappeared from the catalog, and you need to know who removed them

    What to do. Open “Account” → “Operation log” in “All records” view. In the “Date” column filter, enter the day when the products might have disappeared (or the month, for example 2026-08), and in the “Operation type” column, enter “Product”. Look for a row where the “Info” column says “Bulk product deletion: removed:” followed by a number.

    What you get. The row shows who deleted them (the “User” column), when, and how many items.

    What you won't get. The row has no names of the deleted products — only the count. There's no way to bring the products back: they have no trash, and the records are erased from the database. The row itself stays in the log for no more than 14 days.

    A manager deleted the wrong order

    What to do. While the “Documents deleted: N” message is still visible at the bottom (it stays for 12 seconds), click “Undo” in it. If the message is already gone, open the menu in the document list header → “Document trash”, find the batch by date and author, and click “Undo” in its row.

    What you get. The whole batch comes back: the documents with their items and the links between them. The batch row in the trash gets the “Restored” mark. If the document's internal ID has been taken by another document in the meantime, the restored one gets a new ID, and the links within the batch are preserved.

    What you won't get. Neither the deletion nor the restoration of a document is shown in the “Operation log”. A posted document can't disappear this way at all: until it's unposted, deletion won't work. Batches older than 30 days are erased during the next document deletion, and the trash window shows only the 30 most recent batches.

    A supplier was accidentally deleted from the contact list

    What to do. In the contact list, open the “Deleted” → “Trash” section in the left panel, select the card, and click “Restore”.

    What you get. The card returns to the list together with its documents, price lists, and history: nobody touched them while it was in the trash. A “Restored from trash” event appears in the card's history.

    What you won't get. The “Operation log” has no row for this kind of deletion — the only trace is in the card's own history. After 60 days in the trash, the card is erased automatically, and “Delete permanently” erases it right away. You can't delete your own company at all.

    A product's price or description changed, and you need to know what it was before

    What to do. In the “Operation log”, find the row for that product — with the type “Product” or “Product edit” — and click the clock icon at the end of the row. An edit to a cell in the product grid is labeled in the “Info” column as “Field changed in the product table: …” with the field code, and opening the card as “Product card opened”.

    After you click, “Operation history” opens, narrowed down to that product. For a document, the way in is the same — the “Operations log” item in the document card.

    What you get. The expanded row shows the fields that changed: the old value in red, the new one in green, with the date and user next to them.

    What you won't get. A price list import doesn't record value history, and a base catalog update records it only when “Value change history” is turned on in the settings. Product photos, attributes, and categories aren't shown here. Old values are kept for 7 days.

    What to do when you can't find it in the log

    What you see, why it happens, and what to do
    What you seeWhyWhat to do
    “This window is closed for your permission group. Ask the system administrator — access is granted in Group permissions.” The user's group doesn't have permission for the “Operation log” window Grant the permission in the group settings (about access)
    The “User” column is empty The row wasn't written by a person: a scheduled run, a request from an external system, or a background job Look for the cause in the operation itself, not in a person (how to search)
    A product disappeared, and there isn't a single row about it in the log The product deletion row doesn't contain names — only the count, so you can't find it by searching for the product name Narrow down by date, “Operation type” = “Product”, and “Operation subtype” = “Delete” — this finds both single and bulk deletions. Elbuz has no trash for products (about what deletions leave behind)
    The log is empty for the date you need Rows older than 14 days are cleared. Site parsing rows are kept for 3 days at most, and rows for one source are erased when the next run for it starts Scroll to the very bottom of the list and check the date of the last row — that's how far back your log goes; there's no data beyond it (about retention)
    You clicked “Restore” and got “Restore failed” The history record is already gone, the product was deleted in the meantime, or the fields already have the values they had before the edit. Restore works only for products Open the product card and check whether the product exists and what values its fields have now (about restoring)
    The price changed, but the “Operation history” window is empty Value history is recorded only for manual edits — of a card, a grid cell, a bulk value set for selected products, or a document. The nightly price list import and base catalog update don't write to it. For categories, the window is always empty Check how the price moved in the product price history, and look for the run itself in the “Operation log” (about change history)
    “Trash is empty - no documents deleted in the last 30 days” Either no documents were deleted, or the snapshot is older than 30 days and has already been erased The document can no longer be restored; create it again (about the document trash)
    “The records and all their links will be erased for good. Selected:” The confirmation for the “Delete permanently” button in the contact trash Cancel if you're not sure: after this action there's no way to restore (about the contact trash)

    FAQ

    Price list imports and parsing have been stuck for an hour. How do I stop everything at once?

    In the “Operation log”, open the “Additional operations” menu → “Stop all operations” and confirm. The job queue will be cleared completely, and anything unfinished will have to be started again. To stop a single price list, use “Stop import” in its row in the “Price lists” window.

    How do I find out who deleted a product?

    Narrow down the log by date and “Operation type” = “Product”, and type “Delete” in “Operation subtype”: this finds single and bulk deletions with the author and time. Product names aren't shown there, only the count, and the product can't be restored.

    How long is the log kept?

    Log rows — up to 14 days, “Operation history” — 7, document trash — 30, contact trash — 60, site parsing rows — up to 3. These periods can't be changed. The full table is in the section about retention.

    Can I restore deleted items from the log?

    No, the log only tells you what happened. Restore deleted items from the document trash (30 days) or contact trash (60). For products, categories, and everything else, deletion is final; the last resort is the nightly database backup, which rolls back the whole database (about what deletions leave behind).

    Why is the “User” column sometimes empty?

    That's how rows not written by a person are marked: a scheduled run, a request from an external system, a background job. There's no specific employee behind such an action.

    Can a manager see other employees' actions?

    Yes. The window has no filter by author: anyone with permission for the “Operation log” sees everyone's work. You get access to the whole log or none of it.

    Where can I see what a field's value was before an edit?

    In the “Operation history” window — the clock icon at the end of a product or document row. The history is kept for 7 days and is recorded only for manual edits: a price from the nightly run isn't shown here.

    The “Restore” button said “Restore failed”. Why?

    Restore works only for products, and it fails when the history record is already gone, the product was deleted, or the fields already have the old values. A successful rollback says “Updated”.

    Where to find it and who has access

    There is a single window, and in the menu it lives under “Account”. It has no ready-made desktop shortcut — you open it from the menu or from other windows, and you can add a shortcut yourself if you need one.

    Menu
    Account → Operation log
    From bulk-processing windows
    the “Operation log” button in AI bulk text generation; the “Log” button in automatic product enrichment and in the AI media studio
    From an export or import template card
    the “Run history” button — the same data for a single template
    Access permission
    the “Operation log” window; anyone who has it sees the actions of all employees
    Trash
    permission for the document list or the contact list
    Setup
    none: the log is kept automatically, and you can search it within the retention period
    Main menu with the Account section expanded, showing the Operation log item
    1Account section
    2Operation log
    1. Account — the menu section that holds the log and other personal tools.
    2. Operation log — opens the journal window.

    “Operation history” and the trash have no menu item of their own at all — you can open them only from inside other windows. Where exactly is covered in the sections on change history and on the trash.

    The log has no separate permissions inside it, and no “only my actions” filter: you get access to the whole log or none of it. “Operation history” and the “Restore” button check the same “Operation log” permission. The “Delete permanently” button in the contact trash also requires the delete permission. For groups and checkboxes, see the article on access rights.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free