See what ran, what it held and what it cost

Operations answers three questions on three tabs: what ran (Operations), what money it held (Authorizations), and how the money moved (Ledger). The tab and the filter are part of the address, so a list you filtered is a link you can send.

What ran

An operation is one model call that was allowed to spend: the model call of an AI Model node of a flow. A call refused before its hold is not an operation.

An operation is pending while it runs, then completed or failed. It is uncertain when the provider was asked and Slen never learned how the call ended: the provider did not answer in time, or it ran a model call of a flow in the background and Slen could not get its result. The hold of such an operation stays until it expires, because the provider may have been paid: check the call with the provider.

An operation can stay pending after its execution has ended. A flow waits 72 hours, by default, for a model call the provider runs in the background and still reports as running. Then the execution is closed as failed with parked_expired, and the operation is left as it was.

Find an operation with Search operation ID or user…. An operation ID finds that operation however old it is: the period does not apply to it, and the page says so when the operation lies outside it. Any other text finds the operations of your customer whose ID is that text or starts with it, within the period. The search is part of the address as well, so what you type stays in the history of the browser.

Narrow the list with Status, Operation and Period. A period is at most seven days, and the list opens on the last seven. Reset brings the list back to that.

The list is read page by page, the newest first. Choose 10, 25, 50 or 100 rows with Rows per page: under the table; the console remembers the choice. The pages after the first stay as they were while you read them: an operation that starts meanwhile is added to the first page. Columns shows or hides the status, the customer and the start of each row, and can add the time of the last change and the whole operation ID. The console remembers the columns in this browser.

One operation

Open a row to see the operation on a page of its own. Its title is the operation code, and the whole operation ID stands under it with a button to copy it. The strip under the title adds the attempts up: Provider cost is the exact sum of what the attempts cost, the tokens are counted in and out, Provider latency is the time of all the attempts together, and the last number is how many attempts there were.

Provider attempts shows every call to a provider in order, one card each: the model, the connection with the name of the provider pool that chose it (the mark pool when the name is not known), the status and the error code of a failed attempt, the tokens, the cost and the time it took. A failed attempt that the provider billed has a cost too. A member who may open connections can follow the connection to its page. View attempt details opens the rest of what is known about an attempt: its ID and the request ID of the provider, both to copy, when it ended, why the provider stopped, the cost multiplier and the price version.

Request details names the operation code, your customer, and when the operation was created and last changed. For the model call of a flow it also names the execution and the node the call belongs to, and a member who may open flows can follow it to the execution.

What it held

The Authorizations tab lists the holds of the model calls of the last seven days, newest first. Estimated is what a call was expected to cost, Held is its hold and Captured is what it cost. How budget reservations work says what each status means. This tab and the Ledger tab are read page by page, as the operations are.

How the money moved

The Ledger tab lists the entries of the last seven days, newest first: every hold, release and capture adds one. Attempts is the number of calls to providers a capture paid for. A hold and its capture are both positive, so do not add the entries up — Ledger entries explains each type.

Where to go next

• How budget reservations work — what a hold does to a budget.

• Operations — the same holds over the API.

• Ledger entries — the same entries over the API.

• Inspect an execution — the run of a flow behind an operation, node by node.

• Analytics — the spend and the outcomes of the requests over a period.