Actions work queue
Review upcoming, pending, completed, and expired DALP actions from the operator queue.
The Actions page is the operator work queue for tasks that need attention now, tasks scheduled for later, and the history of tasks that finished or expired.
Open it from the sidebar at Actions or go directly to /actions.
Use this page to answer one operational question: what can my current account act on, what is coming next, and what already happened?
The list refreshes every few seconds while the page stays open. This makes it useful during active settlement, maturity, redemption, yield, and KYC operations.
What appears in Actions
The queue combines on-chain actions and account-level actions that are visible to your authenticated user in the active organization system.
Current action types include:
| Type | What it covers |
|---|---|
| Mature bond | Confirming a bond maturity action |
| Redeem bond | Redeeming a matured bond position |
| Claim yield | Claiming yield from a yield-bearing bond |
| Approvals | Maturity allowance, yield allowance, and XvP settlement approval actions |
| 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 actions | Action records that can be listed but are not yet executable from the portal |
Each row shows the action type, the action name when it differs from the type, target address, status, activation time, and expiry time when applicable.
Completed rows also include execution time and executor address when those fields are available.
On-chain and off-chain rows look different
On-chain rows target a token, feature, settlement, or other contract address. KYC update rows are off-chain account actions, so they do not show an on-chain target address.
Access and execution permissions
Users must be signed in to the onboarded DALP portal and have access to the organization system to view the Actions queue. The listed actions are scoped to the active system and the authenticated user.
Execution also depends on the row:
- The action must be Pending.
- The action type must be supported by the portal.
- On-chain actions need the address the action flow uses. Some yield and maturity allowance rows route through the underlying token address even when the action target is a feature contract.
- Account-level KYC update requests are off-chain actions and open the KYC update form instead of an on-chain transaction flow.
- Wallet verification, token state, settlement state, allowances, expiry, and action-specific validation can still block or reject execution after the row appears.
If an action cannot be executed from the portal, the row shows Unavailable or disables execution instead of opening a transaction flow.
Status tabs
| Tab | Statuses shown | Default order | How to use it |
|---|---|---|---|
| Pending | Pending | Activation time, newest first | Work that is active now. Supported pending actions 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 actions are shown with completed history because they no longer require action. They remain useful for audit review and operational follow-up.
XvP approval rows use the caller's current settlement approval state. If you approve a settlement, your approval row moves to Completed with your approval time and wallet. If you revoke that approval before execution, the same row can return to Pending because the approval is no longer active. XvP execution rows use the settlement execution record and stay completed after execution.
Execute a pending action
Review the row
Check the action type, name, target address, activation time, expiry time, and status before acting.
For KYC update requests, the row is shown as an account action because it does not target an on-chain contract address.
Execute the action
Click Execute on a supported pending action.
The portal opens the action-specific flow:
- Bond maturity confirmation for maturity actions
- Redemption for redeem actions
- Yield claim for claim-yield actions
- Allowance approval for maturity and yield allowance actions
- KYC update form for KYC requests
- XvP approval or execution flow for settlement actions
If the action type cannot be executed from the portal yet, the row shows Unavailable instead of an executable action.
Recheck the queue
After execution, return to the Actions page. The queue refreshes automatically, and the action moves out of Pending when the underlying operation is complete.
If your session expires or the portal receives an unauthorized response, the page stops polling until you sign in again.
Search, filter, and export
The table includes search, filters, column controls, pagination, and CSV export. Use these controls to narrow the queue by action name, type, date fields, target, or executor fields available in the table.
The Actions page fetches a bounded result set and paginates the visible table. Use filters when the queue is busy so the row you need is visible in the current operational context.
Token-specific actions
Some token detail pages also show the Actions component scoped to that token.
Token-scoped views show actions whose target matches the token address for that page. Use them when you are operating from a specific token and only need actions for that token.
Account-level KYC actions only appear in the main Actions queue. KYC actions do not have an on-chain target address.