Scheduled tasks in Hummerce are processes the store runs on its own, on a schedule, without staff involvement: ERP synchronization, search index rebuilds, checking payment and delivery status, feed exports, and other background work. Store staff see them all in one place in the panel - they can check when a task last ran, run it manually, and read its log when an integration suddenly stops working.
As of Hummerce 2.27-2.35, updated 2026-09-29.
¶ Benefits and use cases
- One place for all background processes - store staff see the status of every synchronization and integration, without asking a developer "did this go through yet".
- Fast diagnosis of integration failures - the task log and the error info from the last run show the cause right away, instead of waiting for the next cycle.
- Manual run instead of waiting for the schedule - e.g. after changing an integration's configuration or fixing the cause of an error.
- Temporarily pausing a task - disabling it during maintenance work without changing the integration's configuration.
- Access via the AI assistant - staff can ask directly "did the ERP sync succeed" or request a task run in a conversation with the assistant, without opening the panel.
- The list is in the Status -> Tasks menu and shows every scheduled task registered in the store.
- A filter shows all tasks, only active ones, or only currently running ones.
- Sorting by run frequency, last run, next scheduled run, name, or task order.
- The history of previous runs expands under the task name and stays open even after refreshing the list.
- For each task you can see: whether it's enabled, whether it's currently running, whether the last run ended in an error, the time of the last and next scheduled run, and the frequency.
¶ Running and disabling a task
- Run now - the same task that normally starts on schedule starts immediately. A task that's already running or disabled is skipped - it can't be run a second time in parallel.
- Enable / disable - a disabled task keeps its schedule but is skipped at every scheduled run, until re-enabled.
- Task log - messages recorded during recent runs and the full description of the last error (including its technical cause) - the primary source of information when an integration (e.g. Allegro, a courier, ERP) stops working correctly.
- Search index - a full search index rebuild once a day at night (2:00 AM by default), plus separate, more frequent updates (e.g. virtual categories every hour).
- Payments - recurring PayPal payment status synchronization (every few minutes), Przelewy24 (once a day), and checking the status of installment and leasing applications.
- Deliveries - recurring retrieval of shipment status from couriers (e.g. every few hours, depending on the integration).
- ERP integrations - importing items, customers, prices, stock and invoices, and exporting orders and statuses as independent tasks, each with its own frequency set during the integration's implementation.
- Marketplace - the Allegro integration exchanges data (retrieving events, importing orders and offers, updating offers, exporting stock and statuses, sending sales documents) through more than a dozen separate tasks, each of which can be disabled independently.
- Prices and configurators - a daily currency exchange rate update, recurring cleanup of the price list price cache, recalculating configurable set prices, and background processing of ordered configurations.
The general list in Status -> Tasks is for preview, manual run and the log. The frequency and on/off switch for a specific integration task are sometimes also available in that module's own settings group in the store configuration (e.g. Configuration -> Scheduled tasks for installment integrations) - alongside the general list, not instead of it.
- The scheduled task list has been part of the panel for a long time; the current view (filtering by state, sorting, expandable run history) - since version 2.27.
- Handling scheduled tasks via the AI assistant (MCP) - since version 2.35.
- Each task is part of a specific module (integration, search, price list) - a task appears on the list only after that module is enabled in the store.
- Access via the AI assistant requires a running AI assistant (MCP) and task permissions on the account it's connected with.
- Works right after an update - the task list, manual run, log and AI assistant handling are part of the platform, with no implementation work.
- A new scheduled task requires implementation - a new synchronization or integration meant to run automatically in the background is part of that integration's module. Implementation time and frequency are set together with that module (e.g. an ERP integration or a courier), not separately.
- The list only shows tasks registered in a given installation - a module disabled in the store configuration has no task there.
- A task that's already running or disabled is skipped when a manual run is attempted - it can't be run a second time in parallel.
- The frequency of most tasks is set during module implementation, not independently on the general list - only selected integrations have their own frequency settings group.
- The AI assistant runs, stops and reads the log of existing tasks with the same permissions as the panel account it's connected with - it does not create new tasks or change their schedule.
- We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).
- Setting each task's frequency directly on the general list, without separate per-module settings.
- Notifying store staff when a task ends in an error.
Can a scheduled task be run manually, without waiting for the schedule?
Yes, with the "run now" button on the task list - it works exactly like a scheduled run, just immediately.
Can the AI assistant (MCP) run or stop a task?
Yes, with the same permissions as the panel account it's connected with.
Can you check why an integration stopped working?
Yes. The task log shows recorded messages and the full description of the last error - the first place to check when there's a synchronization problem.
Does disabling a task change its schedule?
No. A disabled task keeps its schedule but is skipped at every scheduled run, until re-enabled.
How long does adding a new scheduled task take?
It depends on the module it relates to - a new task is part of a specific integration or synchronization, so we quote the implementation time with that module, not separately for the task itself.
Want to check which background processes are worth running in your store? Contact the Hummerce team (in Polish).
- Status -> Tasks - task list with a filter (all / active / running), sorting, expandable run history, manual run and on/off switch.
- Configuration -> Scheduled tasks - for selected integrations (e.g. installments and leasing), a separate settings group with an on/off switch and frequency for that task.
¶ REST API and MCP
MCP (AI assistant - MCP server):
ec2_tasks_list - the task list, exactly as on the panel screen: enabled, running, time of the last and next run, error from the last run; optionally only tasks with an error.ec2_task_log - the log of a selected task: recorded messages and the full description of the last error.ec2_task_run - run a task now (a disabled or already running task is skipped, just as in the panel).ec2_task_set_executing - enable or disable a task.
The tools use the same permissions as the panel account the MCP key is assigned to.