# Actions work queue
Source: https://docs.settlemint.com/docs/operators/runbooks/actions-work-queue
Review upcoming, pending, completed, and expired DALP actions from the operator queue.
The operator work queue tracks pending work, scheduled items, and the history of completed or expired entries.
Open it from the sidebar or go directly to `/actions`.
Use this page to answer one operational question: what can your current account execute, what is coming next, and what already happened?
The list refreshes every few seconds while the page stays open, making it useful during active settlement, maturity, redemption, and KYC operations.
## What the queue shows [#what-the-queue-shows]
The queue combines on-chain operations and account-level items visible to your authenticated user in the active organization system.
The table below lists current queue entry types.
| Type | What it covers |
| ------------- | ---------------------------------------------------------------------------- |
| Mature bond | Confirming a bond maturity step |
| Redeem bond | Redeeming a matured bond position |
| Claim yield | Claiming yield from a yield-bearing bond |
| Approvals | Maturity allowance, yield allowance, and XvP settlement approvals |
| XvP execution | Executing an XvP settlement after the settlement is ready |
| KYC update | Account-level KYC update requests that open the KYC update form |
| Other | Queue entries that can be listed but are not yet executable from the Console |
Each row shows the entry type, name, target address, and status. Activation and expiry times appear when applicable.
Completed rows also include execution time and executor address when those fields are available.
On-chain rows target a token, feature, settlement, or other contract address. KYC update rows are off-chain account
items, so they do not show an on-chain target address.
## Access and execution permissions [#access-and-execution-permissions]
Users must be signed in to the onboarded DALP Console and have access to the organization system to view the queue. Listed items are scoped to the active system and the authenticated user.
Execution also depends on the row:
* The item must be Pending.
* The entry type must be supported by the Console.
* On-chain items need the address the execution flow uses. Some yield and maturity allowance rows route through the underlying token address even when the target is a feature contract.
* Account-level KYC update requests are off-chain items and open the KYC update form instead of an on-chain transaction flow.
* Wallet verification, token state, settlement state, allowances, expiry, and item-specific validation can still block or reject execution after the row appears.
If a row shows "Awaiting custody approval", DALP has recorded the operation as pending on the custody path. Treat it as a status row while the custody provider approval or signing process finishes. The row is not executable from this queue.
If an item cannot be executed from the Console, the row shows "Unavailable" or disables execution instead of opening a transaction flow.
## Status tabs [#status-tabs]
| Tab | Statuses shown | Default order | How to use it |
| --------- | -------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------- |
| Pending | Pending | Activation time, newest first | Work that is active now. Supported pending items show an Execute button. |
| Upcoming | Upcoming | Activation time, newest first | Work that is scheduled for a future activation time. |
| Completed | Executed and expired | Execution time, newest first | Operational history. Executed rows include completion time and executor address when available. |
Expired items appear with completed history because they no longer need attention. They remain useful for audit review and operational follow-up.
XvP approval rows reflect the caller's current settlement approval state. Approving a settlement moves your approval row to Completed, recording your approval time and wallet. Revoking that approval before execution returns the same row to Pending. XvP execution rows use the settlement execution record and stay completed after execution.
## How the tabs keep executable work in view [#how-the-tabs-keep-executable-work-in-view]
The queue opens on the Pending tab, so executable work appears first. Each tab loads only its own statuses, so future-dated Upcoming rows never push your pending rows onto a later page.
Within each tab, rows use a default order suited to that status:
1. Pending: activation time, most recent first.
2. Upcoming: activation time, most recent first.
3. Completed: execution time, most recent first, covering both executed and expired history.
Sorting a column applies your chosen order to the rows in the current tab. Clear the sort to return to that tab's default order.
## Open a specific tab from a link [#open-a-specific-tab-from-a-link]
The active tab is reflected in the page URL, so you can link or bookmark a view that opens straight on the tab you need.
| Address | Opens on |
| ------------------------ | --------- |
| `/actions` | Pending |
| `/actions?tab=pending` | Pending |
| `/actions?tab=upcoming` | Upcoming |
| `/actions?tab=completed` | Completed |
When you switch tabs, the URL updates to match, so copying the current URL shares the tab you are looking at. A link with no tab parameter, or with a value other than `pending`, `upcoming`, or `completed`, opens on Pending rather than showing an error.
To point a colleague at scheduled work, send `/actions?tab=upcoming`. To point them at history, send
`/actions?tab=completed`. The link opens on that tab with its rows already loaded.
## Execute a pending item [#execute-a-pending-item]
### Open the queue [#open-the-queue]
Navigate to the work queue from the sidebar. The page opens with the Pending tab selected.
### Review the row [#review-the-row]
Check the entry type, name, target address, activation time, expiry time, and status before acting. For KYC update requests, the row appears as an account item because it does not target an on-chain contract address.
### Execute [#execute]
Click Execute on a supported pending row. The Console opens the flow for that entry type. Unsupported types show Unavailable.
Each entry type launches a specific flow. Token-lifecycle types use bond maturity confirmation, redemption, yield claim, or allowance approval. Account-level KYC requests open the KYC update form. Settlement types open an XvP approval or execution flow.
### Recheck the queue [#recheck-the-queue]
After execution, return to the queue. It refreshes automatically. The row moves out of Pending when the underlying operation is complete. If your session expires or the Console receives an unauthorized response, the page stops polling until you sign in again.
## Search, filter, and export [#search-filter-and-export]
The table includes search, filters, column controls, pagination, and CSV export. Use these controls to narrow the queue by name, type, date fields, target, or executor.
The page fetches a bounded result set and paginates the visible table. Because it opens on the Pending tab, ready work is in view without setting a filter. Use filters and search to narrow a busy tab to a specific name, type, date range, target, or executor.
## Token-scoped queue [#token-scoped-queue]
Some token detail pages also show the queue scoped to that token. These views show only entries whose target matches the token address for that page, so use them when you are operating from a specific token and only need its items. Account-level KYC items only appear in the main queue because they have no on-chain target address and cannot be filtered by token.
## Related guides [#related-guides]
These guides cover the specific flows you launch from this queue. Each guide walks through a single operation type with step-by-step instructions, prerequisites, and the verification outcome to confirm the operation succeeded.
Review the settlement state and submit your approval. All required parties must approve before execution can proceed.
Execute a settlement once all required approvals are in place. The settlement must reach a ready state first.
Complete or update requested KYC information to satisfy verification requirements.