Today's run stopped
Nothing in your store changed. A run stops when a file is missing or something looks wrong. Open Home, select Review the run, and find its code below.
A stopped run changes nothing in your store. Your products, prices and stock stay exactly as they were. The app stops a run on purpose when an EJD file is missing or a safety limit says something looks wrong, because a bad file could otherwise reprice or hide thousands of items.
A run is the app's daily comparison of EJD's files with your store (see the glossary).
- Open Home. The banner The last catalog run stopped says why. You also get an alert, and an email if you set one in Settings > Alerts.
- Select Review the run to open it. Its status is Stopped, and the banner gives the code and the numbers.
- Find the code below and follow its steps.
Most stops clear on their own. You can't restart a stopped run, and you don't need to: the next run starts by itself when EJD's next file arrives, or you can select Start a run now on Catalog. Each run works from EJD's latest files, so nothing is lost.
Find your code
- STOP_FILE_MISSING: a file the run needs isn't here yet
- STOP_ROW_COUNT: EJD's file looks incomplete
- STOP_DISCONTINUED_LIMIT: too many items would be discontinued at once
- STOP_RECLASS_LIMIT: too many items would move between online and store-only
- HOLD_RESTRICTION_CONFLICT: EJD's restrictions file contradicts itself
- STOP_MASS_PRICE_CUT, STOP_MASS_HIDE and STOP_MASS_RETURN: not a problem. The run waits for your OK on big price cuts, hides, or discontinued items coming back. See A run waiting for your OK
- STOP_FORMAT_CHANGE: EJD changed a file's layout
- STOP_BASELINE_NOT_SAVED and WARN_BASELINE_NOT_SAVED: the record of the last run couldn't be saved
- STOP_APPLY_STILL_RUNNING: the previous run was still writing
- STOP_NEWER_FILE_BLOCKED: EJD's newest file failed its checks
- STOP_FILE_DAYS_DIFFER: EJD's two files are from different days
- STOP_RUN_CRASHED: the run stopped partway while comparing
- STOP_DEALER_FILE_HELD, STOP_DEALER_FILES_STALE or STOP_DEALER_CLOSED: a problem with your own EJD account's files
STOP_FILE_MISSING
The app doesn't have a usable copy of a file the run needs. The banner says which:
- No EJD login connected yet, or no file from it yet. Your catalog and costs come from your own EJD accounts. Connect your logins in Settings > EJD feed (see Your EJD logins). If they're already connected, wait: the app checks each login a few times a day, and the run starts by itself when the first file arrives.
- A shared EJD file: EJD's product file for your warehouse, its store-only file, or its restrictions file. Usually EJD is late, or the file it sent failed its checks. Striven watches these files and is alerted when they're late or fail. You don't need to do anything. The next run starts when a good file arrives.
If it's still stopped the next day, contact support.
A file from the wrong warehouse
The online feed must come from the warehouse your store follows (IL01 unless you chose another) and the store-only feed from WA01. A file from another warehouse would make thousands of items look moved or discontinued. The app rejects such a file when it arrives and never uses it. A run only ever reads the file for your own warehouse, so if no good one is left, it stops with STOP_FILE_MISSING.
STOP_ROW_COUNT
EJD's file lists more than 10% fewer items than your store has EJD items. That usually means EJD sent a partial file. Nothing was written. The next run starts when a complete file arrives.
If it's still stopped the next day, contact support with the numbers from the banner.
STOP_DISCONTINUED_LIMIT
The run would discontinue more of your EJD items than your Stop if discontinued above (%) limit in Settings > Pricing and safety (5% unless you changed it).
- Read the banner on the run. It says how many items would be discontinued, out of how many.
- Ask yourself whether that's believable. Did EJD really drop that much of your catalog?
- If it doesn't look right, do nothing and contact support. A wrong or partial file is the usual cause. The next good file runs normally.
- If support confirms it's real (for example, EJD dropped a whole line), raise the limit just above the share in the banner, select Save pricing and safety, then select Start a run now on Catalog. Check the run's Discontinued tab before you apply it.
- Set the limit back afterwards. It's there to catch bad files.
STOP_RECLASS_LIMIT
The run would move more of your EJD items between online (ECOM: items EJD ships to your customers) and store-only (BRICK: items EJD only delivers to your store) than your Stop if moving online/store-only above (%) limit in Settings > Pricing and safety (3% unless you changed it). A month of real EJD changes moves under 1%. Thousands at once almost always means EJD's two files don't match, so the run stopped before any item lost its online listing.
- Read the banner on the run. It says how many items would move, out of how many.
- Do nothing and contact support, unless you know EJD moved a whole line to store-only.
- If support confirms it's real, raise the limit just above the share in the banner, select Save pricing and safety, then select Start a run now on Catalog. Check the run's Shipping tab before you apply it.
- Set the limit back afterwards.
HOLD_RESTRICTION_CONFLICT
EJD's restrictions file lists an item you carry more than once, with different values. The whole run stops. See Held: restriction conflict.
STOP_FORMAT_CHANGE
EJD changed the layout of a file, so the app set it aside instead of reading it wrong. See A file changed format.
STOP_BASELINE_NOT_SAVED
After each run writes to your store, the app saves a record of EJD's data as of that run. The next run compares today's files with it. This time the record couldn't be saved, so the run stopped: planning against an older record could make the same changes again, including over a price you set by hand since. Nothing reached your store.
You don't need to do anything. The next run tries to save the record first. If you see this again tomorrow, contact support.
WARN_BASELINE_NOT_SAVED
A run wrote its changes to your store, but the record of what it wrote couldn't be saved. Your store is fine. The next run saves the record before it plans anything, and stops with STOP_BASELINE_NOT_SAVED if it still can't.
STOP_APPLY_STILL_RUNNING
The previous run was still writing to your store, so today's run waited for it. After about 6 hours it stopped, rather than plan against changes that weren't finished. Nothing reached your store from this run.
Open Catalog to see the run that's still writing. If it hasn't moved, contact support.
STOP_NEWER_FILE_BLOCKED
EJD's newest product file failed the app's checks, so it was held back. The run stopped rather than use the older file in its place, because mixing yesterday's online list with today's store-only list would show items moving that didn't. Nothing reached your store.
Striven is alerted to every held-back shared file. You don't need to do anything: the next good file from EJD starts a run by itself. The EJD's files card on Catalog shows which file was held back and why.
STOP_FILE_DAYS_DIFFER
EJD's online (ECOM) and store-only (BRICK) files are from different days. EJD posts them minutes apart, so the run waited about 3 hours for the matching file before stopping. Nothing reached your store. The next run tries again once both are from the same day.
If it keeps happening, EJD may have stopped posting one of them: contact support.
STOP_RUN_CRASHED
The run stopped partway while comparing EJD's files with your store, for example because Shopify's read of your products didn't finish. Nothing was written. The next file or scheduled run tries again by itself. If it happens two days running, contact support.
A problem with your own EJD files
These three codes are about the files from your own EJD account. Each has its own section in Your EJD logins:
- STOP_DEALER_FILE_HELD: your newest file was held or failed its checks.
- STOP_DEALER_FILES_STALE: your newest file is more than 14 days old.
- STOP_DEALER_CLOSED: one of your EJD accounts is marked closed.
Technical details
Show the exact rules, for the technically minded
- Every check that can stop a run happens before anything is written, so a stopped run never leaves your store half-updated.
- The checks run in this order: previous run still writing, saving the last run's record, your own EJD files (closed account, no file, file older than 14 days, newer file held), shared files missing, newer shared file blocked, files from different days, then the safety limits after planning.
- STOP_ROW_COUNT: today's catalog has fewer than 90% as many items as your store has EJD items.
- STOP_DISCONTINUED_LIMIT counts discontinued items against your store's EJD items (items already in your store plus those being discontinued). Products that aren't from EJD don't count.
- STOP_RECLASS_LIMIT stops only when the moves are more than your limit's share of your EJD items and more than 500 items. Under 500 moves never stops a run, whatever the store's size.
- STOP_APPLY_STILL_RUNNING: the run checks again every 10 minutes, 36 times (about 6 hours), before it stops.
- STOP_FILE_DAYS_DIFFER: the run checks again every 20 minutes, 9 times (about 3 hours). The day is the date EJD stamps in each file's name.
- STOP_RUN_CRASHED is also set by the app's watchdog when a run has been comparing for more than 3 hours.
- STOP_ROW_COUNT, STOP_DISCONTINUED_LIMIT and STOP_RECLASS_LIMIT alert your store only. They don't raise a separate alert to Striven.
- A run that would use exactly the same files as one already planned, waiting or applied doesn't run again.