Approvals, failures and rollback

Transcript

In this episode, nothing goes out without your say, and a failed run recovers without doing anything twice. You’ll answer a question, approve or decline what goes out, and retry a failed run safely.When a run is missing something, it asks the person who knows, then carries on. Open this morning’s run from Runs. Dispute 1047 has no dock log, so the AOP can’t confirm the arrival time. Instead of guessing, it stops and asks. The question appears in the run. Marcus, the dock lead, knows the answer, so he opens the run on the web. He types the arrival time and attaches the gate log. When he clicks Submit, the same run picks up where it paused, with his answer in hand.Nothing goes out until you say so. The AOP drafts the carrier email from Jordan’s mailbox, then waits for his review. Jordan checks the recipient and the subject, sees the evidence pack is attached, and fixes one line. Then Approve and send. The tracker shows it as sent. The next draft has the wrong contact. Jordan opens Feedback, chooses Decline with feedback, and says why. That email is never sent. The AOP marks the dispute Held, with the reason. In this AOP, every carrier email waits for its own decision.A Salesforce change happens once, only after you approve it, and Athena checks that it landed. First it says exactly what it plans to change, and waits. Jordan approves. It makes the change using a Northwind account set up for it, so it can only do what that account is allowed to do. Open the browser beside the run, then Action log, to see every step it took. Then it looks at the record again, and marks the dispute done only when the change is really there.A failed run picks up where it left off, and never sends twice. Filter Runs to Failed, and open the error under the row. Here the AOP couldn’t open the tracker, because the tracker wasn’t shared with it. Share the tracker with the AOP’s owner, then click Retry This Run. It runs again with the same request. Anything already finished is skipped. An email that went out is not sent again, and the Salesforce change is not made a second time.If the agent gets an edit wrong, you can undo only that change. Here, its edit to dispute 1049 was wrong. In the tracker’s Activity, choose Select changes to roll back. Tick that change, click Rollback, and confirm. Then check the result, and look over the sheet. Know the limit. Rollback can’t unsend an email or undo the Salesforce change. It only undoes changes inside Athena. That’s why the email and the Salesforce change both waited for your approval before they happened.Quick check. Can rolling back the tracker unsend the carrier email? No. Rollback only undoes changes inside Athena.Here’s how a finance team uses this. Their invoice AOP stops when a receipt is missing, and asks the person who has it. Every supplier email waits for review. When a run fails, they fix the cause and retry, and nothing is done twice.Now try it. Add this line to an AOP of your own. When it works, the run stops for your review before anything goes out.

​

Before you start

Upload these files from the Northwind starter kit: All files in Lesson 16: the tracker, email file, dock log, claim form, and dock photos; plus Northwind dispute SOP.pdf and Workspace setup.txt. Prepare the lesson 15 procedures from the setup guide. Email sending and record changes need approved access; ask your admin for a sending mailbox and a practice account. Without them, review a draft on the web and skip sending or changing records. Answer questions on the web if text messaging is unavailable. Retry and rollback need actual runs and edits; uploads alone cannot supply that history.

​

Steps

​

Try it

Before you send anything or change any record, check whether it’s already done, show me the change, and wait for my approval.

Look for the run stopping for review before anything goes out.

​

Next

Answer from governed numbers