MMartechFlow

Run history and statuses

Read your feed's run history, understand each status from fetching to done or error, and tell a manual run apart from a scheduled one.

What a run is

Each time a feed refreshes, MartechFlow records a run. A run captures when it started, when it finished, how it was triggered, the product counts it processed, and an error message if it failed.

Your run history shows the most recent runs, newest first. Use it to confirm a refresh actually happened, see how many products came through, and diagnose a failure.

Run statuses you will see

A run moves through several in-progress stages and ends in either Done or Error. The in-progress labels are friendly versions of the underlying processing stage.

  • Fetching: MartechFlow is downloading your source feed.
  • Reading: it is parsing the file (CSV, XML, or XLSX).
  • Bypassing block: the retailer blocked the first fetch attempt, so MartechFlow is trying a fallback route so your feed still updates. This is automatic; no action needed.
  • Importing: rows are being matched and written into your product catalog.
  • Done: the run finished successfully. Image rendering and export rebuilds then follow automatically.
  • Error: the run failed. The history row shows the error message, and a breakage alert is raised for the feed.

Manual vs scheduled runs

Every run records how it was triggered. A scheduled run was started automatically by the feed's refresh schedule. A manual run was started by you (the run button) or by a programmatic API refresh call.

This lets you tell apart 'the schedule is working' from 'someone kicked it off by hand', which is useful when you are debugging timing or confirming that an automation fired.

What happens after a run finishes

A successful run does not stop at importing. It chains into image rendering (applying your templates) and then export rebuilds, so the public pull URLs end up serving the new data. This is why a 'Done' import is quickly followed by your exports rebuilding.

If a run fails, the chain stops and the feed keeps serving its last good exports. A failed import or a failed export build raises an alert so you find out without watching the screen.

A successful run also clears any open 'refresh failed' alert for that feed, so the alert list reflects the current state rather than a problem you already fixed.

Related

Questions

How many runs are kept in history?

The run list shows the most recent runs for the feed, newest first. Older runs age out of the visible list but the latest activity is always there.

A run says Done but my product count looks low. What happened?

A Done status means the import succeeded, not that the catalog grew. Check the run's product counts and compare to the previous run. A sharp drop can trigger a count-drop alert, and a very large drop can hold the export to protect your channels.

What does 'Bypassing block' mean and is it a problem?

Some retailers block automated fetches on the first try. MartechFlow automatically retries through a fallback route so your feed still updates. It is informational; you do not need to do anything.

My run errored. Where do I see why?

Open the run in history; the error message is stored on the run. You will also get a feed breakage alert with the same reason. Fix the underlying cause (often a bad source URL, a blocked source, or a parsing issue) and run again.

Can I see runs through the API?

Yes. The public API exposes a feed's runs at GET /api/v1/feeds/:id/runs, returning the same status, trigger, counts, and timing fields.

Ready to try it?

Start free, no credit card. Your first feed can be live in minutes.

Start free