↑↓ selectEnter openEsc close

    1. Elbuz

    How to run an export manually or on a schedule and read the log

    15 min readUpdated

    Elbuz runs exports by button, all at once or overnight on a schedule, and logs every run — how many products went out and where a run stumbled.

    When you need this:

    • Several channels must update on their own — the schedule runs enabled templates, skips disabled ones.
    • A channel is still being set up — run a disabled template by hand; the schedule won't touch it.
    • A run was started by mistake — “Stop” breaks it off at the nearest boundary.
    • The last run didn't happen — the number on “✦ AI” flags it; the consultant names the reason.

    Where to start: template list → template row → “Export”.

    What running an export can do

    Running by hand and on a schedule

    One template

    Select a row in the list and click “Export”, or hover over the row and click the triangle “Export this template”. Both show a summary, and only after you confirm does the program say “Export started — follow it in Operations”, and a row for this run with its log appears in the Operations center.

    A single template started by button runs in this browser tab's request: don't close or reload the tab until the log reaches “Data export completed”. “Export all templates” and the schedule run in the background on the server — there you can close the tab.

    The template card header has a button with the same label, “Export”, and it behaves differently: it saves the form and asks “Start the export” with a single line: “Products going into the file: N. The new file replaces the current one at the permanent link.” The run starts after you click “Export” in that window.

    • If the template filter can't be counted quickly or the count request itself fails, you'll see “?” instead of a number — even then the run starts only after you confirm.
    • There's no full summary here: to see all the figures before sending, close the card and run the template from the list row.
    • To check from the card there's a different button — the flask “Check”: it sends nothing.
    • The Elbuz Tunnel template card has no “Export” button in the header: a tunnel is run from the list row, where the full summary opens.

    Stop rules live on the server, so a rule in “Stop the export” mode stops a run started from the list or the card alike. If such a rule has already fired, the card button starts nothing and shows the red message “Export stopped by a stop rule: ‹rule code›. Check stock statuses in the base catalog.”

    The message names the rule by its internal code: stock_drop — a stock collapse, vol_drop — a collapse in the number of products, vol_empty — nothing to export. What the thresholds mean is explained in the article on stop rules.

    Two ways into a manual run: at the top, the list row with the full summary; at the bottom, the card header with a single number. Both lead to a run on the server, where stop rules fire regardless of what was shown
    button is inactive while arun is in progressnoyesfilter not available for a fastcount, or the request failedyesyesnoExportExportyesnoExport“Export” button in the list rowNothing happensIs “Show the summary beforestarting an export” on?Run on the server — stop rules arechecked againWas the summary counted?“Preflight summary skipped” —“Export” or “Cancel”Did a rule in “Stop the export” modefire?Dialog with only a close button — norun“What will be exported” dialog —“Export” or “Cancel”“Export” button in the card headerThe form is savedDid a rule in “Stop the export” modefire?Red message “Export stopped by astop rule” — no run“Start the export” — product count,or “?” if the summary wasn't counted
    • Action or result
    • Decision: the path depends on the answer

    Even a disabled template can be run by hand: the “State” switch limits the schedule and the bulk run, not your button. This is how you test a channel that's still being set up.

    All templates

    List menu → “Export all templates”. Only active templates are taken, one after another, in the order of the “Processing order” column. The run is in the background, so you can close the window. The whole bulk run shares one limit — an hour; run heavy templates that don't fit separately or spread them out on the schedule.

    On a schedule

    Use the “Schedule” button in the “Related settings” section of the template card.

    Know two things in advance. First, the schedule skips disabled templates — the “State” switch overrides it. Second, two scheduled exports never start together: the second job sees the first and logs “Scheduled export canceled because another template is being exported (data processing conflict).” Spread several heavy templates out in time.

    An overnight scheduled run: the first check cancels the whole job, the next two skip only a single template, and then the queue moves on
    yesnonoyesyesnoThe schedule starts the export jobIs another scheduled export stillrunning?Log: “Scheduled export canceled…”— the job doesn't runNext template in the job's listIs the template enabled?Template skipped, no line in the logDid a rule in “Stop the export” modefire?Run stopped — the old file staysExport by the template
    • Action or result
    • Decision: the path depends on the answer

    Stop

    The operation row in the Operations center has a “Stop” button. It doesn't kill the process instantly: the stop flag is checked between steps, so the run ends at the next boundary. The log shows “Export stopped by the user!” (a warning, not an error), and the operation card closes with that line. The “Last export” date stays unchanged.

    Run log and run history

    The run log lives in the Operations center and shows lines in real time — the export window isn't blocked meanwhile. The order of steps is fixed, so you can see how far the run got:

    For XML and Google feeds it is: “Exporting data...” → “Product indexing” → summary → “Export product categories” → “Export products” → “Export products ‹N› of ‹M›” → “Uploading file to cloud storage” → the “Download file ‹name›” link → “Data export completed” and “Time elapsed: ‹hh:mm:ss›”.

    The set of steps depends on the template type: lines about photos, the description generator and email sending appear only where those steps exist at all. The line “Export products ‹N› of ‹M›” matters most: it's a fact, not the summary's forecast.

    Export template check window: product ID field and the result of a trial run
    1Product ID field
    2Result line
    1. Product ID — leave it empty to check the template on the products it selects, or enter an ID to see whether that product gets in.
    2. Result line — the trial run does not send anything; here it reports that no product matches the template conditions.

    Among the first lines, right after “Product indexing”, the log writes the summary: “Preflight summary: ‹N› products total, ‹N› in stock, ‹N› out of stock, ‹N› pre-order, ‹N› without stock status.” — and, when there's something to compare with, “Previous run: ‹N› total, ‹N› in stock.” This also works for scheduled runs, when nobody saw the dialog.

    At the end, the log gives the “Download file ‹name›” link — the same one the “File” column shows.

    The log window shows the current run. Lines from past runs don't vanish from the database — they're kept for two weeks, and operation cards for three months; to see what happened earlier, use the chart button “Run history”, found both in the list toolbar and in the template card header.

    Each run is registered separately in the Operations center as a card labeled “Data export” together with the template's type, name and file name; in a bulk run, the template cards sit as children under a shared “Export of all templates” card.

    The “Run history” window shows the template's runs for the last 30 days — up to the 50 most recent.

    If the export completion sound is turned on in the settings, the program plays a signal at the end of the run.

    The template's “✦ AI” button: why the export didn't happen

    When a template is selected in the list, the “✦ AI” button appears in the toolbar. It opens a chat with suggestions about this template: “Template run history” (if the template has run before) and “Check the template on a product”.

    An orange number on the button means the last run had a problem:

    • “the last run was cancelled — another export was running”;
    • “the last export failed”;
    • “3+ runs cancelled in 7 days because of another export”.
    The AI button in the Export window toolbar with its tooltip
    1AI button
    2Tooltip
    1. AI button — opens a chat with AI about the selected template.
    2. Tooltip — explains that AI can tell why an export failed, show run history and check a product.

    Clicking the badged button sends an analysis at once: the consultant reads the run log and names the reason. The number then turns grey until the set of problems changes. If runs get canceled by other exports, the chat opened from the exports window offers “Schedule without conflicts”: it shows what runs simultaneously and suggests another time (about the schedule).

    Scenarios

    Six sales channels, and all should update on their own

    What to set up: in each template, set the “State” badge to “Active” and set a schedule with the “Schedule” button. Spread heavy templates out in time.

    What you get: when the time comes, the schedule runs the enabled templates and skips the disabled ones. You no longer need to click anything. What won't happen: two scheduled exports don't run at once — the second job is canceled with a line about a data processing conflict.

    The channel is still being set up, but you need to see the file

    What to set up: leave the template disabled and run it with the “Export” button in the list row.

    What you get: the run goes ahead, and the file lands at the template's link. What won't happen: the schedule and “Export all templates” skip a disabled template, so it won't run again on its own.

    A run was started by mistake

    What to set up: click “Stop” in the operation row in the Operations center.

    What you get: the run ends at the nearest boundary between steps, and the log shows “Export stopped by the user!”. What won't happen: the half-built file goes nowhere — the previous one stays at the link, and the date in the “Last export” column doesn't change.

    What to do when a run didn't happen

    What you seeWhyWhat to do
    “Scheduled export canceled because another template is being exported (data processing conflict).” The schedule saw that another export was still running Spread the template schedules out in time (about the schedule)
    “No file was produced. Fix the problem above first — while it is there, no products get into the export.” The run failed before it got to building the file Fix the error named in the line above in the check log
    “Export stopped by the user!” Someone clicked “Stop” in the Operations center; the run ended at the nearest boundary Nothing: the previous file stays at the link. Run the template again when you're ready

    FAQ

    What happens if I run a disabled template?

    It gets exported. The “State” switch limits scheduled runs and “Export all templates”, while the “Export” button on a specific template works in any state.

    I clicked “Export” in the template card and no summary opened. Why?

    The full “What will be exported” summary opens only when you run from the list row. The card header button only asks for confirmation with the number of products. To see all the figures before sending, run the template from the list.

    How long is the log of past runs kept?

    Log lines are kept for two weeks, operation cards in the Operations center for three months. You can open them with the chart button “Run history” in the list toolbar or in the template card header.

    Why didn't the “Last export” date change after a run?

    The date changes only after a successful run. After the “Stop” button, or when no file was produced, the old date stays (where the file goes).

    How is running one template different from “Export all templates”?

    A single template runs in any state. “Export all templates” takes only active ones and runs them in the background in turn, in the order of the “Processing order” column.

    Where to find it and who has access

    Menu
    Directories → Operations → Data export
    Other ways in
    Operations center — the log and “Stop”; “Schedule” in the template card
    Access right
    the “Data export” window
    Prepare
    a configured template; for the schedule — the “Active” state

    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