Why a scheduled check sits in collecting

A scheduled check that shows "collecting" for longer than you expected isn't stuck — it's usually just waiting on its batch window or on fresh data to come in.

What you get

• A status that always reflects what's actually happening to your run, not a generic "in progress" spinner.
• A predictable reason for every long "collecting" period, so you can tell normal from actually-stuck.
• The same run history and detail page for scheduled runs as for any other run, so you can check progress any time.

What "collecting" means

"Collecting" is the stage where a run gathers the source data it needs — pricing, availability, and promo information for every item in scope — before handing off to the checks that turn that data into alerts and recommendations. A manual run usually moves through this quickly. A scheduled overnight run can sit in "collecting" for longer, because it's also waiting for its place in the overnight batch window rather than being processed the moment it's queued.

When a long "collecting" is normal

• The run was triggered by an overnight schedule, not Run now — overnight runs are expected to take longer and finish by morning.
• A source you rely on (like a slow retailer site) is taking longer than usual to respond for some items.
• Your workspace has a large catalog, so gathering data for every item simply takes more time.

When to check further

If a scheduled run is still showing "collecting" well past your usual overnight window, or a same-day Run now stays there for an unusually long time, open the run's detail page in Reports & history — it shows exactly where the run is and whether anything needs your attention.

Go further

• Overnight checks finish by morning — why overnight runs use a batch window.
• Put checks on a schedule — how scheduled runs get triggered in the first place.
• Run a check & read a recommendation — what happens after collecting finishes.