# How do timed transitions work in Adalo?

Use timed Adalo transitions for intentional loading or confirmation states while preserving a manual escape path, predictable navigation, and clear feedback.

- Canonical URL: https://adalocado.com/answers/timed-transitions
- Verification: Legacy video — current verification pending
- Topic: Actions and Logic
- Skill level: Beginner
- Last reviewed: 2026-08-12
- Index status: improve-first

## Short answer

Use a timed transition only for a short, predictable state such as confirmation or onboarding, and ensure the destination does not depend on unfinished work.

## Intended outcome

A short-lived screen that advances reliably and remains accessible.

## Requirements

- Source and destination screens
- A reason not to use an immediate link

## Step by step

1. **Keep the state short**

   Use a clear message and avoid hiding important input behind a timer.

2. **Configure the transition**

   Follow the legacy video as historical reference and confirm the current builder’s available screen actions before shipping.

3. **Provide an escape**

   For anything longer than a brief confirmation, allow the user to continue manually.

## Why it works

- Timed navigation is presentation, not a substitute for confirming that asynchronous work succeeded.

## Common failures

### The screen advances before data is ready

Move navigation after the relevant successful action rather than relying on elapsed time.

## Testing checklist

- [ ] No user input is lost
- [ ] Destination data is ready
- [ ] Reduced-motion and accessibility needs are respected

## Limitations

- This legacy resource has not completed the current editorial and builder verification workflow.
## Sources

- No external sources are listed yet.

Markdown version: https://adalocado.com/answers/timed-transitions.md