Workday’s Platform Consumption Console can warn you that Flex Credits are running out. It does not turn the agent off for you. This guide sets out what Workday documents about default alerts, custom budgets, who receives them, and what still has to happen by hand.
What Workday sends by default
On the Alerts and Budget page of the Platform Consumption Console, Workday documents:
- Default alerts at 80%, 90%, and 100% of the active credit threshold.
- Delivery to users who can access the Management Dashboard: Platform Consumption Console domain, plus a banner on the console itself.
- Custom alerts you can add for specific agents on a weekly, monthly, or annual credit budget. If you do not pick named recipients, Workday sends those custom notifications to everyone with that domain.
Usage on the console is not real-time. Workday updates usage daily starting at 2:00 PM UTC for the previous day, and the calculation can take up to three hours. An agent that burns credits late in the day may not show on the dashboard until the next daily refresh.
What an alert does not do
Workday’s admin guide states plainly: Workday does not deactivate offers on the Platform Consumption Console when you exceed your credit entitlement. To stop an agent, someone with the right access must deactivate it through the agent registration path Workday documents for Workday-built agents (Register and Configure Workday-Built Agents), or change the custom agent’s availability in Agent System of Record / Agent Management Hub for agents you built.
So an alert is a signal to a person. It is not a kill switch.
Who must be on the list
Put people who can actually stop spend on the domain and on custom alert recipients:
- The administrator who can deactivate or restrict the agent.
- The owner of the Flex Credit purchase (often Finance or the Workday subscription owner).
- For a custom agent that loops on tool calls, the developer who can change the agent’s design in Extend.
If only a reporting analyst can see the console, the alert reaches the wrong desk.
Why custom agents make this urgent
The public Flex Credits Rate Card (last updated November 5, 2026) meters customer-built agents by invocation and by tool call. Custom agent invocations are 1 / 2 / 3 Flex Credits for Base / Standard / Premium model tiers. Tool calls are priced per 100 calls, with higher rates when Custom Agents use Advanced tools. A misconfigured agent that retries the same tool can burn credits without a human noticing until the next day’s console refresh.
Practical setup
- Confirm UMSA and that Flex Credits apply to your agreement (Flex Credits are for UMSA customers).
- Grant Management Dashboard: Platform Consumption Console to the people who buy credits and the people who can deactivate agents.
- Add a custom alert for each high-spend agent (Sana, a Recruiting skill at 750 credits per unique requisition, or any Production custom agent) with a weekly budget below your remaining entitlement.
- Write a one-page runbook: who gets the alert, how they verify the agent in Agent System of Record, and who has authority to deactivate it the same day.
- Do not rely on Sandbox console numbers for Production spend. Workday says non-Production tenants track consumption for information for most offers, while Production balances generally reflect Production usage—except for named agents such as Deployment and Adoption that also consume credits in listed non-Production environments.
What this guide does not claim
Workday’s Rate Card is informational and is not your contract. Your Order Form and the Flex Credits and Platform Entitlement Policy (or Complimentary Flex Credits Policy) decide what you actually pay. Confirm exact recipients and deactivation steps in your tenant’s security configuration; Workday’s public pages do not list every customer’s security group names.