On schedule, Elbuz imports price lists, updates the catalog, exports to marketplaces, gets exchange rates, backs up the database — like your button. Long operations finish in the background.
When you need this:
- Dozens of sources need daily updates — one nightly schedule imports all, updates the catalog, builds exports.
- A supplier updates several times a day — its source schedule picks it up at set hours.
- A marketplace has its own timetable — the export template gets its own schedule.
- Prices unchanged by morning — the operation log shows if a run happened and why not.
Where to start: price lists → menu → “Schedule setup” → “Active”.
What a schedule can do
- Starts work at a set time — you build the rule from words, no need to type it by hand.
- Runs the nightly chain “price lists → catalog → exports” with one schedule.
- Builds a flow from the steps you pick, in the order you need — when you don't want to export every template.
- Finishes long operations in the background — in the job queue, in parts.
- Explains why a run didn't happen — with a log entry and six checks.
- Restores product values after a failed run, if value history was turned on beforehand.
What this gives your business is covered separately: what it does for your store.
Schedule and job queue are different things
Both run in the background, and people call both “automation”, but they answer different questions.
- The schedule answers “when to start”.
- The job queue answers “what has started but not finished”.
An operation that can't finish within one request — bulk text generation, auto-enrichment, AI matching — doesn't wait for a schedule: it becomes a queue job right away and is finished in parts. How to track it is covered in the job queue article.
The queue itself is processed on a schedule too — every minute. This system schedule needs no setup: it's a safety net, so unfinished work gets done even if the process that started it broke off.
Besides your own schedules, the “Job schedule” list has a few system jobs (cache cleanup, tickets, KSeF and others). One of them is “Marketplace orders”, whose interval you can change. The job queue, triggers, and email retrieval run on service schedules that aren't in the list.
Three price lists with the same “at 3:00” rule are one run, not three. The app groups schedules by the “job type + rule” pair and passes the whole list of sources to the handler at once. So spreading schedules out in time only makes sense between different types of work; identical ones with the same rule run together anyway.
How to set the run time in the schedule window
The window is small and looks empty at first. At the top are the “Active” checkbox and the rule builder; below them, three read-only fields: “Current server date and time WEB”, “Current server date and time DB”, and “Time zone”. At the very bottom is “Note”, free text for yourself.
1
Active2
Rule builder3
Time zone4
No save button- Active — while it is off, the program ignores the schedule.
- Rule builder — the rule is assembled from words, no need to write it by hand.
- Time zone — the time in the rule is understood in this zone.
- The form has no save button here: changes are saved automatically.
This window has no “Save” button, and that's not an interface bug. The form saves itself as soon as you change anything. People look for the button, don't find it, and close the window thinking “not saved” — but everything is saved, including an accidental click in the builder.
You build the rule from words: “Every week on Monday at 10:00”. Nothing to type by hand, and you won't see a string of asterisks anywhere. The builder has one limit that is sometimes taken for a bug: several minutes within an hour can be selected only for order imports and import templates — everything else gets one minute per hour.
You can, however, select several hours, several days of the week, several days of the month, and several months.
The schedule row is created turned off the moment you first open this window. A rule is filled in right away — 17:10, Monday to Friday — so it looks as if everything is already set up. It isn't: while the “Active” checkbox is cleared, the app doesn't see this schedule at all.
Now about the two time fields and the Time zone field. They're there for a reason: “10:00” means 10:00 in the time zone of the admin user, not in the time zone of whoever creates the schedule, and not in your browser's.
If people in different countries share the account, check the time against what the window shows, not against the clock on your computer.
Where to see the result
There's one place: “Account” → “Operation log”. Both scheduled runs and the job queue write there.
1
Operation type2
Filter row- Operation type — look for queue, export and price list load records here.
- Filter row — type a value above a column to narrow the list.
Search by operation type. The job queue is logged under “Job queue”; schedule refusals are logged under the type of work that didn't run: “Export”, “Price list import”, “Import”, “Site parsing”.
A price list also has its own run log — the “Log” tab in the source card, with figures for every import and a step-by-step breakdown of the latest one. If the schedule ran but you don't like the result, look there: what the supplier sent this time.
One more case, unrelated to the log. A price list for customers — a file at a link — is updated only by a template run. Until a run happens, the customer sees what was built last time. If the schedule for such a price list is off, the customer gets the file from the last manual run.
If a nightly run has already damaged data
There's no “undo the nightly run” button. What you can restore depends on one switch, and it had to be on before the run: “Value change history” in “Account” → “System settings” → “Catalog” → “Data processing rules”. It's off by default.
If the switch is on, the base catalog update — scheduled or by button — takes a snapshot of product field values before it starts and, afterwards, records the before and after values for each changed product. To find what was affected:
- In the “Operation log”, open the menu and choose “Operation history”.
- In the filter row above the “Date” column, enter the date of that night as
2026-09-26— that's how it's stored in the column. Only products changed on that day remain. Expand a row to see the old and new field values. - The “Restore” icon in a product row brings back its “before” values. The app asks: “Restore the previous field values of this product? This cannot be undone.”
1
Date filter2
Restore- Date filter — enter the date of the night here.
- Restore — returns the product to its previous values.
One click restores one product: this window has no bulk rollback. Records are kept for 7 days — a run that damaged data a week ago can't be undone this way. If the product was deleted after the run, restoring returns “Restore failed: the record is missing, the product was deleted, or this type cannot be rolled back.”
If the switch is off, the app didn't keep the old values, so there's nothing to restore product by product. The same goes for template imports: they don't write value history regardless of the switch. What's left is the database backup, but it returns the whole database to the moment of the backup — everything done after it is lost.
“Undo” in the base catalog's “Recent actions” window won't help here. It only lists your own bulk edits — field value replacement and find-and-replace, done in the grid or delegated to the AI consultant in chat. Scheduled runs and the job queue don't write to this list.
Scenarios
Update prices from all price lists every night and send them to marketplaces
What to turn on. In the price list list, open the additional actions menu → “Schedule setup”. This is the “Processing price lists” schedule, one for the whole account.
Select “Active” and build a rule, for example “Every day at 03:00”. Then, in “System settings” → “Catalog update” → “Run and general rules”, check two switches: “Update catalog after import” and “Build exports after update”. Both are on by default.
1
Update catalog after import2
Add new products3
Build exports after update- Update catalog after import — without it only the price lists are loaded overnight.
- Add new products — when off, the nightly run does not create new products.
- Build exports after update — closes the chain to the marketplaces.
What happens. At the set time, all enabled sources are imported, then the base catalog is updated, and after that all enabled export templates are built.
If the sources include site that hasn't finished yet, the catalog update waits for it, and the log shows “Price lists loading completed. Batch processing will be launched after parsing is complete”.
Exports then also run after the catalog update, not with stale data.
- Action or result
- Decision: the path depends on the answer
What won't happen.
- No new products appear in the catalog unless “Add new products” is turned on in the same group.
- Sources with a browser-based parser aren't included in the nightly run.
- If a single-source import or a scheduled site parsing is already running at start time, the run is refused with a “data processing conflict” entry until the next night.
If you need to export only selected templates, in your own order, build a flow.
One supplier updates its price list several times a day
What to turn on. Source card → “Settings” tab → “Schedule” card → “Configure”. This is the “Price list processing” schedule for this source only. Select “Active” and pick several hours in the builder, for example 9, 13, and 17: you can pick several hours, but not several minutes within an hour.
What happens. At the selected hours, only this source is imported. If “Update catalog after import” is on, the base catalog is then updated from this one source.
What won't happen.
- New products from such a run aren't added to the catalog, even with “Add new products” on: that switch applies only to the all-price-lists run.
- Export templates aren't built after it automatically — marketplaces need a separate export schedule.
- If “Processing price lists” or another source is running at that moment, the run is skipped; a disabled source or contact is skipped by the schedule with a warning.
Pull data with an import template several times an hour
What to turn on. Import template card → “Schedule setup”. For import templates, the builder lets you select several minutes within an hour, for example 00, 15, 30, and 45.
Marketplace orders need no schedule — they're fetched by a system job.
What happens. The template runs at each selected minute. Several templates with the same rule run in one pass, one after another.
What won't happen. If the previous template import hasn't finished yet, the new run isn't queued — it is skipped until the next selected minute.
Export to one marketplace on its own schedule
What to turn on. Export template card → “Schedule”, the “Active” checkbox, and a rule. The template itself must be enabled.
What happens. The template is built on its own rule, independently of the nightly price list chain. Several templates with the same rule are built in one pass, one after another.
What won't happen. A disabled template isn't built on schedule, and the “Operation log” won't have an entry about it. If another template is being built on schedule at that moment, the run is skipped.
If “Build exports after update” is on, this template is also built at the end of the nightly chain — together with all enabled templates.
What to do when a schedule misbehaves
| What you see | Why | What to do |
|---|---|---|
| The “Operation log” has no entries for the night, or a “data processing conflict” entry | The run didn't start, or was skipped because of another run | Go through the checks in order (schedule didn't run) |
| The schedule window has no “Save” button | The form saves itself as soon as you change anything | Just close the window; check that you didn't touch the builder by accident (about the schedule window) |
| “You have no access to this window. Contact your administrator.” or “You don't have permission for this operation!” | The user's group lacks the “Job schedule” right | Grant the right in group settings (about access) |
| The nightly base catalog update overwrote prices or names | The run did the same as the button would. Old values are kept only if the “Value change history” switch was on beforehand | Open “Operation history”, filter by the run date, and restore products with the “Restore” icon (about rollback) |
FAQ
Which time zone does “10:00” refer to?
The admin user's time zone — not that of whoever creates the schedule, and not the browser's. Check the time against the Time zone field in the schedule window.
Can a schedule run more often than once an hour?
Only for order imports and import templates — there you can select several minutes within an hour. For everything else the minimum step is one hour.
Will the nightly run add new products to the catalog?
Only if “Add new products” is turned on in the “Run and general rules” group, and only in the all-price-lists schedule. A single-source schedule doesn't add new products.
I want to import all suppliers' price lists every morning and export only to Rozetka and Prom. Where do I set this up?
In the ready-made flow “Load supplier price lists and update site/marketplaces”, with two “Export” blocks and a “Schedule” trigger. Step by step — in the flows article.
Does the “Job schedule” list show the app's system tasks?
Partly. Besides your own schedules, it has a few system jobs (cache cleanup, tickets, KSeF and others), including “Marketplace orders”, whose interval you can change. The job queue, triggers, and email retrieval run on service schedules that aren't in the list.
I opened a schedule “just to look”. Did I break anything?
The form saves on any change, including an accidental click in the builder. Check that the rule reads the way you set it and that the “Active” checkbox is where it should be.
Where to find it and who has access
This topic has no menu item — neither the schedule nor the job queue. You open the schedule of a specific item from its card, with the “Configure” or “Schedule setup” button. All schedules in the account are listed in the “Job schedule” window — the “Job schedule” tile in the “Other settings” section of the “System settings” window.
- Menu
- Directories → Flows — the “Flows” window
- Price list source card
- “Settings” tab → “Schedule” card → “Configure” button
- Price list list
- additional actions menu → “Schedule setup” (all price lists and the base catalog update at once)
- Export or import template card
- “Schedule” button (export) or “Schedule setup” (import)
- Price list parser settings
- “Schedule setup” button
- Currency list and backups window
- “Schedule setup” button
- “Translate into other languages”
- “Schedule setup” clock icon in the tab row
- “System settings”
- “Other settings” section → “Job schedule” tile — a list of all schedules in the account
- “Job queue”
- counter in the bottom bar of the base catalog; all entry points are in the job queue article
- Access right
- “Job schedule” in group permissions, plus the right to the item's card
- Prepare
- an item that has been run manually at least once; the correct time zone for the
adminuser
Without the “Job schedule” right, neither the schedule window nor the schedule list opens. If someone can't see a source, template, or parser card, they can't reach its schedule either. In a price list source card, the “Schedule” card also requires the source settings right.
1
Configure2
Auto-load- Configure — the only entry point to the schedule of this source.
- Auto-load — this is where automatic file fetching is set up.
1
Schedule- Schedule — opens the schedule window of this export template.
You can create eight kinds of schedule from the app. Those marked “one per account” can exist only once in an account: trying to create a second one creates nothing.
- “Price list processing” — for one source;
- “Processing price lists” — for all sources at once, one per account;
- “Export products”;
- “Import products”;
- “Parsing products from the site”;
- “Getting exchange rates” — one per account;
- “Database backup” — one per account;
- “Translate into other languages” — one per account.
Related topics
- If the schedule is on but no run happened — schedule didn't run: what to check.
- If an operation went “to the background” and you need to know its status — job queue.
- If you need to choose which templates to export and in what order — Flows.
- If customers get a price list via a link — the file is updated only by a run.
- If you need to translate the catalog on a schedule — bulk translation.
