Failed automation review meeting agenda: a 20-minute run-to-repair check for workflow automation agencies

Short answer

Often only some of them are, and the way to find out is to test three real failures rather than take a yes on trust. A failed run is linked to its repair when the repair record carries the run ID, names the person who fixed it, says what they changed and shows they were allowed to change it. This 20-minute agenda gives a workflow automation agency five timed questions for the client's operations owner and ends with the owner's decision on whether SourceX should screen the company.

Visual briefFull-size diagram
A stopwatch face split into five timed segments with a hand sweeping through them, beside a list of the five agenda questions: sample three failures, run ID in the ticket, who may fix, how long logs last, and the owner's decision.
The 20-minute agenda as a stopwatch. Log retention windows are vendor-documented examples.

It is one of three agendas under the portfolio review meeting agenda for PE operating teams. The hub covers the short version inside a portfolio review; this page is for an agency running its own failed automation review with a client.

Who is in the room

Three people from the client's side, plus you:

  • The automation owner, who sees the failed runs and knows which flows break.
  • The person who repairs them, often an operations analyst or IT administrator. Repairs are where the useful record is, so this person matters most.
  • The operations owner or COO, who joins for the last block, because only the owner decides whether to talk to SourceX.

You chair. Agree in advance that nobody will share run payloads, ticket text or screenshots; you are asking where things are recorded, not to see them.

The 20-minute agenda

TimeBlockQuestionWho answersGood answer
0-3Sample three failures"Pick the last three failed runs. Where is the repair for each recorded?"Automation owner"Two in the service desk, one in a Teams thread."
3-8Run ID in the repair"Does the repair record carry the run ID, or only a description?"Repairer"The ticket template has a Run ID field, and it is filled on two of the three."
8-12Who may fix"Who is allowed to make manual fixes in the target systems, and where is that written?"Repairer or IT lead"Finance ops and two admins, listed in the access policy."
12-16How long the trail lasts"How long do run logs, tickets and chat threads stay available?"IT administrator"Run history about a month; tickets seven years; chat 12 months."
16-20Owner's decision"Do you want SourceX to screen whether these records qualify?"Operations owner or COO"Yes, introduce me." Or: "Not this year."

The first block does most of the work. Three concrete failures turn a general question into a factual one, and the answers in blocks two and three usually follow from what people say about those three.

Why block four has the shortest fuse

Run history is the first part of the trail to disappear. Microsoft's troubleshooting guidance says Power Automate stores flow run data for 28 days, after which runs no longer appear in the run history. Zapier's data retention policy lists 29 to 69 days for Zap run metadata in a customer's account. Other tools differ, so ask the administrator for the actual setting.

Once those windows pass, the only surviving link between a failure and its repair is whatever the repairer wrote into a ticket or a change record. That is why the run ID question in block two matters: a ticket that quotes the run ID keeps the pair joined long after the automation tool has forgotten the run. A ticket that says "fixed the invoice sync" does not.

Illustrative scoring of the three sampled failures

Fictional example: a 180-person wholesale distributor whose agency maintains about 60 flows. Notes taken in the meeting, answers only:

Sampled failureRepair recorded inRun ID in the repair recordRepairer authorized in writingStill traceable after the run log expires
Invoice sync timeoutService desk ticketYesYes, finance ops in access policyYes
Duplicate customer createdService desk ticketNo, description onlyYesPartly, by date and customer
Approval step skippedTeams threadNoUnclearNo, once chat retention passes

One clean link, one partial, one broken. That is a typical and useful result: the client has a repair habit worth describing, and a gap it can see. The agency's note to the owner reports exactly that and nothing about the content of any run.

The decision the meeting should produce

The operations owner chooses one of three outcomes, and you record it with a date:

  1. Screen it. The owner asks for an introduction to SourceX for a fit screen. You submit it through your partner account after registering and signing the Channel Partner Agreement.
  2. Fix the habit first. The owner wants run IDs in every repair ticket before talking to anyone. Agree a review date.
  3. No. Note it and continue the normal automation work.

The agency never decides for the client, and the decision is never a condition of the agency's ongoing work.

Fit, authority and what stays unknown

Before block five, check the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

The operations owner can authorize the conversation; the records may also involve the systems' business owners and, where tickets hold personal data, the privacy lead. Whether the repair history can be licensed, and whether anyone wants it, stays unknown until SourceX reviews it. For context on why automation history matters, see AI agents for back-office automation; for a broader client meeting format, the annual client advisory meeting agenda and the AI strategy offsite agenda fit a longer session, and the portfolio operations review agenda suits investor-led meetings.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the operations owner chose "screen it," register as a partner, confirm the baseline on who qualifies and read the program terms before you send the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why sample only three failures?

Three recent failures are enough to see whether the client's repair habit is consistent, and they keep the meeting short. If all three repairs carry the run ID, the habit is probably real; if none do, the answer is clear without counting more.

Should the agency extend run-history retention before the review?

Only if the client asks for it under its own retention policy. The agency can point out that run logs expire within weeks; keeping anything longer is the client's decision, not something to do because records might be licensed later.

Sources

  1. learn.microsoft.com/en-us/troubleshoot/power-platform/power-auto…
  2. zapier.com/legal/data-retention-deletion
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment