Daily

Catch Adobe Commerce orders that have stalled

A daily email names orders still pending or processing after two days, so none sit unnoticed.

Runs: Daily
Apps: Adobe Commerce
AI: Not needed
Access: sales read

Send this to your assistant

Create a ClickRuntime automation: every day at 9am, email me the Adobe Commerce orders that have been 'pending' or 'processing' for more than 2 days, with order number, customer and how long they've waited.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

An order that stays in Processing for six days is rarely good news. It might be waiting on stock that never arrived, a warehouse that never received the export, or a payment capture that failed quietly. In your Adobe Commerce catalog, these orders are not obvious: they sit in the grid mixed with hundreds of healthy ones, and the customer finds out first, by emailing to ask where their parcel is.

Each day, the automation searches orders by status and by updated_at, picks out those whose status has not changed for the number of days you choose, and sends the list by email. Each row shows the order number, status, customer and how long it has been stuck.

It is useful for operations managers and small teams where one person does fulfillment on top of other work.

What you get out of it

Customers are contacted before they complain
If you reach out first with an update, the customer sees a proactive shop. If they have to chase you, they remember it, and often leave a poor review. A quick message from you turns a potential complaint into a mark of good service.
Hidden process failures are found
Many stuck orders share one cause, such as a broken integration with the warehouse. A list of them makes the pattern clear, so you fix the cause once instead of each order by hand.
Payment issues are caught in time
Orders waiting on a pending payment may need a follow-up before the item is reserved too long. Spotting them early prevents lost sales and inventory held for no reason. A held payment can also mean stock reserved for someone who will never complete the order.
Fulfillment staff have a clear to-do list
The email is a short list of orders to investigate, so the person on duty knows where to start instead of scrolling through the order grid. There is no filtering, sorting or guessing involved.
Fewer refunds and chargebacks
A customer waiting two weeks with no news may dispute the charge. Catching late orders early gives you the chance to ship, update or refund before a dispute starts. It also protects your standing with the payment processor.

How it works

What happens, step by step

Once a day, ClickRuntime looks for Adobe Commerce orders that have sat in the same status without an update for too long.
It works out how many days each of those orders has been waiting.
You get an email listing each one with its order number, customer, current status and how many days it has been stuck.

Before it runs live

Connect Adobe Commerce

What you get

RunsDaily

Catch Adobe Commerce orders that have stalledtoday, 9:00Succeeded

Email · Stuck orders- #000004712 Dana Fox (processing), 4 days

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Adobe Commerce steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

stale_order_status_alert.pyexample

from datetime import datetime, timedelta
from clickruntime import on_trigger, credentials, http, notify

BASE = "https://yourstore.com/rest/V1"
F = "searchCriteria[filter_groups][{}][filters][0][{}]"

@on_trigger
def run(event):
    cutoff = datetime.utcnow() - timedelta(days=2)
    params = {F.format(0, "field"): "status", F.format(0, "value"): "pending,processing",
              F.format(0, "condition_type"): "in",
              F.format(1, "field"): "updated_at", F.format(1, "value"): cutoff.strftime("%Y-%m-%d %H:%M:%S"),
              F.format(1, "condition_type"): "lt", "searchCriteria[pageSize]": 500}
    orders = http.get(f"{BASE}/orders", params=params,
                      headers={"Authorization": f"Bearer {credentials.secret('ADOBE_COMMERCE_TOKEN')}"}).json()["items"]
    if not orders:
        return {"stale": 0}
    lines = []
    for o in sorted(orders, key=lambda o: o["updated_at"]):
        waited = (datetime.utcnow() - datetime.strptime(o["updated_at"], "%Y-%m-%d %H:%M:%S")).days
        lines.append(f"- #{o['increment_id']} {o.get('customer_firstname', '')} {o.get('customer_lastname', '')} "
                     f"({o['status']}), {waited} days")
    notify.email_me(f"{len(orders)} orders stuck for over 2 days", "\n".join(lines))
    return {"stale": len(orders)}

FAQ

Common questions

How many days counts as stale?

You choose. Many stores use three days for Processing and seven for Pending Payment. The number lives in the filter, so each status can have its own threshold. Orders with a long shipping window can have a higher limit than orders for in-stock items.

Which statuses are checked?

Typically the open ones, such as pending, processing and on hold. Complete, closed and canceled orders are normally excluded because they are not expected to change. You can adjust the list to match your custom statuses.

Will an order that was only edited count as moved?

The check uses updated_at, which Magento changes on many edits, including comments added to the order. If that hides real problems, your AI assistant can compare the status history instead. A status history check ignores edits and only counts real movement between statuses.

What permissions does it need?

sales read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Daily