Some products did not change after a schedule ran

Open the run in Run history and read the reason under each product that did not change. Then click Retry if the button is there.

What you see

• On a one-time schedule where no product changed: a banner at the top of the schedule page, for example "Run failed: 3 products didn't change", with a Retry button.
• The run in Run history is marked Completed with issues or Failed.
• In the same case, a card on Home reads "«Schedule name» failed", with "3 of 3 products didn't change." under it, for example, and an Open log button.
• In the bell: "“Schedule name” had issues".
• An email with the subject "«اسم الجدولة» تمت مع مشاكل: … ما تغيّرت" ("“Schedule name” finished with problems: … not changed"). PopAutomate emails to Salla and Zid stores are in Arabic. The email lists up to 5 products that did not change, each with its reason.

Why it happens

If Salla or Zid refuses a product, PopAutomate carries on with the rest and writes the reason under the refused product.

Open the schedule, then the run in Run history, then the Changes tab. Under each product that did not change, a line gives the reason.

Fix

The product is not in your store

The reason "This product isn't in your store. Check its id." means the product was deleted, or its ID in the CSV file is wrong. A retry does not fix it. In the email, the same reason reads "المنتج غير موجود في المتجر، ربما حُذف." ("Product not found in store. It may have been deleted.").

1. Open the schedule and click Edit.
2. Remove the product from the selection, or choose the right product.
3. Click Save changes.

If the schedule starts Now and its status is Offer Active, saving the edit runs it in your store again with the new products. If it is Completed, Ended or Failed, PopAutomate only saves the edit and does not run it. You see "Edit saved. We didn't run it in your store again because it already ran. …". To apply it, click Duplicate and activate the copy.

The platform asked for a delay, or the reason is unknown

If the reason is "Platform requested a delay. We tried 3 times without success." or "We couldn't tell why. Try again, and contact support if it keeps happening.", retry:

1. Open the run in Run history.
2. Click Retry under the product list. Next to the button is the number of products PopAutomate will retry.
3. Click Retry in the Retry? dialog.

PopAutomate retries only the products that did not change, and does not change the schedule's times. The button appears for a run that changed products, not for a run that restored them.

The connection was lost during the run

The reason "Connection to store was lost during execution." means the permission expired in the middle of the run.

1. Reconnect your store with the steps in Store disconnected and schedules paused: how to reconnect.
2. Go back to the run and click Retry.

The product has options

The reason "Product has options, and the platform doesn't accept discount scheduling on options. Retrying won't help." means the platform refused the change on this product's options.

1. Open the schedule and click Edit.
2. Take this product out of the schedule.
3. If you need to, change the product's price in your store dashboard.

If the schedule starts Now, read The product is not in your store to see when saving runs it.

The product changed in your store after the run

When products are restored, you may see "Price changed after execution, so we didn't revert it to preserve your changes." PopAutomate left the product as you edited it. This reason can also appear for a change other than the price, such as visibility or category.

1. If you want to keep your edit, do nothing.
2. If you want to restore the product, edit it by hand in Salla or Zid.

Details in Restore prices and products after a schedule ran.

Zid store, and every product failed

On Zid, the connection can expire while the status stays Connected. Then every product fails, and under them you see "We couldn't tell why…" or "Connection to store was lost during execution."

1. Sign out, then click Sign in with Zid and approve the connection.
2. Go back to the run and click Retry.

Details in Store disconnected and schedules paused: how to reconnect.

If the reason "We couldn't tell why…" appears on a single product, open that product in your store first. It may already be as you want it, for example a product that was already in the category.

Still stuck?

Click Support in the menu on the left. On your phone, tap Contact us in the account menu. The steps are in Contact PopAutomate support on WhatsApp. Send:

• The schedule name and your store name.
• The Change log CSV file from the run.
• A screenshot of the product's reason.

Next: Schedule run results: what changed in your store?, or go back to Fix a PopAutomate problem: where did you see it?.