> ## Documentation Index
> Fetch the complete documentation index at: https://new-docs.squads.so/llms.txt
> Use this file to discover all available pages before exploring further.

# UI Feedback and Delayed Execution

## Overview

Smart Wallets like SquadsX don't execute transactions immediately. This creates challenges for UI feedback and state management in applications.

## Problem

Traditional wallet flows assume transactions execute immediately after signing. Apps often show success messages or update UI state based on this assumption. With SquadsX, the transaction is only proposed for multisig approval, with actual execution occurring later.

## Solution

Don't show errors or optimistic UI state updates if you can't detect the transaction effect. Account for the possibility that transaction execution may be delayed.

When a user signs with SquadsX:

1. The transaction is proposed, not executed
2. Other multisig members must approve
3. Execution happens after threshold is reached
4. UI should reflect the pending state, not assume success

### Implementation Guidelines

* Check actual on-chain state before updating UI
* Provide clear feedback that the transaction is pending approval
* Avoid showing success messages immediately after signing
* Avoid showing error messages when transactions are simply pending

## Related

* [Overcoming Integration Obstacles](/integrations/squadsx/developer-guide/integration-obstacles)
* [Sign-In Requirements](/integrations/squadsx/developer-guide/sign-in-requirements)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.