Fictional data. Rebuilt on every deploy.

City of Acme
Help and guides

City Hall (555) 010-0100

Run the agents

Wake an agent, process the cases that wait, read what it did and put it back to sleep.

Who can do this: Agent Operator. Pick the person to act as them from Demo controls.

Go to Agents

  1. Open "Agents" in the left menu. The counts read "Waiting", "Running" and "Failed". Under "Agent status" each agent reads asleep or awake. The "Incoming" panel lists the cases that wait for the intake agent, and reads "Nothing is waiting." when no case does.
  2. Click "Intake agent" in the left menu or under "Agent status". The heading reads "Waiting work" with the number of cases that wait beside it. Open "More details" to read "Processing" and "Engine". While the agent is asleep the page says "The agent is asleep, so the run buttons are off." Process one and the batch button stay off until you wake it. The batch button reads Process N cases, or Process the next 20 of N when more than 20 cases are waiting, and the note beside it reads "Nothing is waiting" when no case waits.
  3. Click "Wake agent". The button now reads "Put agent to sleep". A woken agent stays awake until a person puts it back to sleep.
  4. Under "Waiting work" click "Process one" on a case, or press the batch button. It reads Process N cases, or Process the next 20 of N when more than 20 cases are waiting. Read the message at the top, then read "Last run" for what the run did. To work a selection of the cases that arrived, open "More tools" in the left menu, then "Intake queue", select the cases and press "Process selected with agent". Open "Signals" on a row of that queue to read what the agent found.
  5. Read "Needs attention" for work that failed, and click "Try again" on a row to run it again. "Recent results" is under "More details".
  6. For the Adjudication agent do the same on its own screen. The recommendations it makes appear under "Waiting for a person". Only a person decides. On the hosted demonstration live Muse is on, with an allowance of 100 live calls per deploy and 100 provider calls a day that whoever runs it can change. When live Muse is off, or that allowance is used up, recorded answers are used and the screen says so.
  7. Open "Steward assistant" in the left menu and click "Wake agent". Its "Waiting work" count shows the tasks of the queue of the Data Steward. Then click "Prepare recommendations" to prepare the work of that queue. The Data Steward reads every recommendation and decides; the operator never decides one. The Data Steward can press "Wake" or "Put to sleep" on "Data issues". Its counts read "High", "Review" and "Held".
  8. Open "Agent runs" in the left menu. Narrow the list with "Agent" and "State". Open "More filters" for "Processing mode" and "Date", then click "Apply filters". Click "Clear filters" to start again.
  9. Click "View run" on a row to open "Run detail". Read "Processing mode", "Processing steps" and "Recorded business changes". A failed run offers "Retry", which needs the agent to be awake. On the agent screen, "All runs", "Processing" and "Engine" are under "More details".
  10. When you have finished, go back to each agent and click "Put agent to sleep". Leave "Steward assistant" awake if a Data Steward still needs it.

What you get: The waiting cases are prepared for a person, and every run is recorded in Agent runs. A run records preparation only: a person makes every permit decision.

All how-to guides