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
| Time | Block | Question | Who answers | Good answer |
|---|---|---|---|---|
| 0-3 | Sample 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-8 | Run 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-12 | Who 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-16 | How 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-20 | Owner'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 failure | Repair recorded in | Run ID in the repair record | Repairer authorized in writing | Still traceable after the run log expires |
|---|---|---|---|---|
| Invoice sync timeout | Service desk ticket | Yes | Yes, finance ops in access policy | Yes |
| Duplicate customer created | Service desk ticket | No, description only | Yes | Partly, by date and customer |
| Approval step skipped | Teams thread | No | Unclear | No, 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:
- 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.
- Fix the habit first. The owner wants run IDs in every repair ticket before talking to anyone. Agree a review date.
- 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.