Actions
Use Actions to review scheduled, pending, and completed work for the active participant, and to run the one control each row actually offers.
This page is the queue of scheduled, pending, and completed operations for the active participant, meaning the person or organisation currently selected in Acting asDelegated Authority lets a signed-in operator work inside another party's account. One check decides who may enter; the party's own roles decide the rest.Read the concept. A row appearing here never means you can act on it: whether this page offers a control depends on what kind of row it is, whether it is still pending, and whether it names a usable target. Come here to run an operation this page can run, or to see what this participant has scheduled or completed. Reach for Activity instead once an operation has finished and you want its indexed on-chain record; this page and Activity answer different questions.
A pending row has one of three control states. A row whose type this Console version recognizes, that is still pending, and that carries a usable target shows an active Execute button. A row waiting on a Custody ApprovalCustody Approval lets you require a decision from your own approvers before a key signs, enforced by the party holding the key, not the platform.Read the concept shows a fixed, static label, never a button; the custody provider's own system does that signing outside the Console. Any row of a type this Console version does not recognize shows a disabled Execute button that reads Unavailable. A Smart WalletA Smart Wallet lets a tenant require several signers to agree before an instruction moves assets, with the rule enforced on chain, not by one private key.Read the concept multisig co-signature request is the case you are most likely to meet: it lands here as a Multisig Approval row and always reads Unavailable, because co-signing happens only on that wallet's own Participant detail page, never on this one.
A Pending row is always one of these three kinds. Only the recognized kind gives you a control to press; the other two tell you where the decision actually happens.
Read the Execute button as a statement about the row, not about your authority: it does not change with your role, and an active button is not confirmation that you are permitted to run the operation. Authorization is decided only after you confirm, by the platform and the contract behind the operation. Selecting Execute and confirming it submits the operation immediately for a row whose panel opens here; you cannot undo it from this page once it starts, and this page keeps no draft state to walk back later.
What this page covers
This page organizes work into three tabs, each with its own sort order. Pending holds active work, soonest first; Upcoming holds scheduled work, also soonest first; Completed folds in both finished and expired rows, sorted most recent first. Each tab's label carries a live count next to it, and the page's URL reflects the tab you are on, so a link to a specific tab reopens on that tab directly. The list itself updates live as events arrive; it does not require a manual refresh. A dropped connection surfaces as an error on the table rather than leaving you looking at a silently stale one, and reloading the page opens a fresh connection; only an expired session prompts you to sign in again.
Every row shows Action, Type, Status, Scheduled, and Expires. The Completed tab also shows Completed and Executed by; the Pending tab also shows the Execute column described above. A custody-pending row looks different from the rest even before you reach the Execute column: instead of normal type and target details, it shows a fixed status pulse indicating the operation is in flight with your custody provider.
Confirm Acting as
Confirm the participant shown in the Acting as control before you read or act on anything. Every row and every available control on this page scopes to that one participant; switching participant changes the entire queue, not just the ones you happen to be looking at.
Choose the status tab
Open Pending for active work, Upcoming for scheduled work not yet active, or Completed for history: executed operations and rows that expired before anyone acted on them. An expired row is not retryable from this page; treat it as closed.
Each tab isolates one stage of work so scheduled and historical rows never crowd out what actually needs attention now.
Identify which of the three kinds the row is
Before you look for a control, work out which of the three kinds a Pending row belongs to. A row whose type is recognized, that is still pending, and that carries a usable target shows an active Execute. A row showing Awaiting custody approval is the fixed status pulse described above; it has no button, only that label, both in the row title and in the Execute column itself. A row whose type this Console version does not recognize shows Execute disabled and reading Unavailable; a multisig co-signature request reaches this queue as a Multisig Approval row and always falls into this third kind.
An active Execute on a recognized row usually opens a sheet right here. Three types leave the page instead. Multisig signer invite normally goes to a dedicated accept screen: it is a different multisig row from Multisig Approval above, an invitation to join a wallet as a new signer rather than a request to co-sign an existing one. Cast vote and Activate voting power normally go to that token's own governance page too, opening a sheet here only when this Console cannot resolve that page for the token involved.
Act only where a control actually exists
Follow the control offered by the row. Select Execute and confirm the sheet for a recognized row that submits in place. For a Multisig signer invite, Cast vote, or Activate voting power row, select Execute and follow wherever it opens: the accept screen for a signer invite, where you choose which of your keys signs for the new wallet, or the token's own governance page for a vote. Otherwise, wait for your custody provider to act on a custody-pending row, or leave this page for the wallet's Participant detail page on a Multisig Approval row.
Before confirming, check the participant and operation. An active button means the Console can open the operation; the platform still checks permission when you submit it.
Troubleshooting
Execute is unavailable
Signal: the Execute button appears greyed out on a row you expected to run. Cause: this page enables Execute only
under three conditions together: the row's type is recognized, its status is currently Pending, and it names a
usable target. Failing any one of those three disables the button, and your role is not one of the conditions, so a
greyed-out button never means a missing permission. Fix: confirm the row's status and type first. A row reading
Unavailable with type Multisig Approval has no fix here; go to the Participant detail page for that wallet
instead. What to check next depends on the type. Cast vote, Cast poll ballot, Activate voting power, Claim yield, Approve maturity allowance, and Approve yield allowance rows don't disable on a missing target: they need
proposal, poll, or token identity the indexer attaches separately, and this page gives you nothing to fix if that
identity never arrived. Every other recognized type does gate on the target shown in the row, so for those, confirm it
is still Pending rather than expired and that it names one.
A custody-pending row has no Approve or Deny button
Signal: a row labelled Awaiting custody approval shows only that fixed label, with no button anywhere in the row.
Cause: this is normal behavior. The decision happens inside your custody provider's own system, outside the Console
entirely, so the row stays deliberately non-interactive here. Fix: open your custody provider directly to sign or
reject the transaction. Watch for a toast reading Custody approval completed or Custody approval failed; no in-row
status text updates, so the toast is the signal to trust.
A row reads Unavailable and I can't find where to sign it
Signal: a Multisig Approval row's Execute button reads Unavailable. Cause: this page never hosts multisig
co-signing; that control exists only on the Participant detail page, under its pending co-signatures section. Fix:
open that wallet's Participant detail page. An eligible signer who has not yet signed sees a Co-sign control there,
showing the current signed weight against the threshold.
A Multisig signer invite's Execute does not open anything, or opens a screen that won't let me join
Signal: selecting Execute on a Multisig signer invite row either does nothing at all, or opens the accept screen
without letting you join. Cause: a silent click means the row's stored invite link no longer matches a shape this
Console can open; nothing on screen reports that failure. Once the accept screen does open, three different states can
block you there instead. An empty key picker means none of your accounts can sign for this multisig yet. A screen
reading Address already in use means one of your keys is already registered as a signer on that draft. Any other
terminal screen means the invitation itself has expired, been revoked by its creator, already been accepted, or
otherwise gone void, and the row can still read Pending here even after that happens. Fix: for a silent click,
reload the page and select Execute again. For an empty picker, create your wallet or add an EOA key account you
control, then open the invitation again. For Address already in use, there is nothing to fix: you are already a
signer on that draft. For every other terminal state, you cannot retry or accept from either screen; ask the wallet's
creator to send a new invitation if you still need to join.
I already signed, but the operation hasn't executed
Signal: on the Participant detail page, the Console records your signature, but the multisig operation has not visibly
executed yet. Cause: reaching the signing threshold does not guarantee an immediate, visible execution. The sheet
shows only a message that the threshold is met and the operation is finalizing. The sheet does not show the later
execution steps. Fix: do not sign again, the sheet will not let you and shows your signature as read-only once
recorded. Wait, then check this page's Completed tab or the Activity page for the operation's eventual result,
rather than expecting this specific screen to update to a final state.
The custody or multisig sheet is stuck loading
Signal: a co-sign sheet shows a preparing state that does not resolve, or briefly errors before recovering on its own.
Cause: a newly created multisig approval can lag behind the row that references it; the Console retries automatically
before it asks you to. Fix: wait a few seconds and let it retry. Select Retry yourself if a prompt is still showing
after that; this is a timing gap, not a sign that the approval failed or that your signature was lost.
Frequently asked questions
Can I run something from the Upcoming tab before it becomes Pending?
No. The Upcoming tab carries no Execute column at all, only Action, Type, Status, Scheduled, and Expires; a control to run the operation appears only once the row's status moves to Pending. Treat Upcoming as a preview of what is coming, not a place to act early, and check back once the row's scheduled time passes and it reappears under Pending.
Why did a Pending row I was about to act on disappear?
Most often someone else acting for the same participant already executed it, or it expired and folded into Completed; the list updates live, so a row can leave Pending between your last look and your click. Check Completed: an executed row shows its Executed by column, and an expired row sits there too, sorted most recent first. Neither state is retryable from this page.
Can I narrow the queue down to one row type when it gets busy?
Yes. The Type filter on the toolbar lists every value the platform's action-type list defines, so Multisig Approval and the custody-pending row are their own named options alongside every type this page can execute. Combine it with the search box, which matches on what is in the Action column, or with the tab you are already on, to cut a long Pending list down to the handful of rows you actually came to work through.