Action Inbox & scheduling
The Action Inbox (/action-inbox) has two main tabs: Prioritised decisions (recommended changes for the current “data week”) and Applied history (what was applied or reverted, when allowed).
Which week is “Prioritised decisions”?
The prioritised list uses calendar logic based on your workspace’s default IANA time zone (configured under Region & time zone, /settings/region-timezone). The app labels weeks using ISO weeks (Monday–Sunday) and focuses on the latest completed week - the most recent Monday–Sunday period that has fully ended in that time zone.
So early in a new ISO week, you are still looking at last week’s completed window until the current week finishes. The UI shows the week code and the Monday–Sunday date range in your workspace zone so everyone agrees which period the list refers to.
Why is my prioritised list empty?
Common reasons:
- Data for that week has not arrived yet. Retail data often lands on a fixed weekly schedule. Right after a new week starts in the calendar, rows can be empty until ingestion completes. Use Schedule help on the Action Inbox (above the list) to see when the next connector sync runs and how it relates to this view.
- Filters. Retailer, network, category, or search filters can hide every row. Try clearing filters if you see a “No actions found” style message for filtered results.
- No actionable recommendations. In some weeks the product may show a message that there are no actionable decisions for that data week (distinct from the “data gap” case).
For other ISO weeks or a wider scan of lines, use the Bidding Grid (/bidding-grid), which is designed to browse across recent weeks.
Schedule help
On the Action Inbox, open Schedule help to read how weekly Retail Connector sync (at 01:00 in the application scheduling time zone, on the sync weekday you choose Monday–Friday in Retail Connectors) relates to the prioritised week. If your workspace default time zone and the application scheduling time zone differ, the help text explains both - they are intentionally separate controls.