Skip to content
All articles

A collection run failed: where to start

Another run is not always the answer. Work from status and logs to the source response, then trial a specific fix.

Akmelo Editorial TeamProduct and data collection
Run error and its diagnostic stepsImage unavailable

After a failed run, pressing Run again is tempting. A source may respond on the second try, but a retry will not fix a wrong field name or changed page structure. First find where the work stopped.

Keep the failed run page open as your reference. Its ID, time, and error text help you compare it with the last successful run. Change one setting at a time so you can tell what helped.

Read the error with the log

Check the final status and failure stage. Was the page fetch, field extraction, validation, or result storage unsuccessful? These need different fixes. Distinguish a partial result from a complete collection too.

Find the first related messages in the Akmelo run log. The last line may only say that execution ended; the useful cause may appear earlier.

For a scenario error, check expected field names, value types, and the active version. If run conditions changed, compare them with the previous successful run.

Inspect the source response

The pages tab shows requested URLs and response details. Open a snapshot if one is available: an error page, access restriction, or different content may have arrived instead of a product card. An HTTP success status alone does not prove you received the intended page.

Do not address an access restriction with endless retries. Check the source's operating conditions and request settings. Not every error is temporary, and retry behavior depends on its cause and configuration.

Diagnose a run through status, log, source response, and a trial fixImage unavailable

Test one hypothesis at a time. If a price appears in a saved response but not in the record, investigate extraction and processing. Fetching the same page again will not fix that.

Trial a small fix

After editing the scenario, run a trial and inspect its fields. Compare several records with their sources, then consider publishing. An error disappearing does not prove that the right data was returned.

If the row count falls, consult the missing product guide. Use the export checklist before delivery. Finally, note the cause, fix, and examples used to verify it so the next investigation starts with useful evidence.