Skip to main content
Tekhabeeb
New Member
Oct 8, 2026 10:44 AM UTC
Question

Best way to model real-time door relay timeouts and badge scan states using Figma Variables?

Hi all,

I'm currently designing an interactive desktop operations dashboard for an enterprise access control system and trying to build an authentic usability testing prototype in Figma.

In our design, operators monitor hundreds of physical access doors and need to run simulated badge-scan overrides. I'm using Figma Variables and conditional logic on an interactive door card component, but I'm running into an issue with state reset timing:

  1. When an operator clicks Simulate Access Granted, the door status variable changes from Idle (Secured) → Unlocked / Door Open for 3 seconds.
  2. After a 3-second delay, the variable needs to evaluate whether a Hold Open toggle is active. If false, it should automatically revert back to Idle (Secured).
  3. If an operator triggers a global Emergency Lockdown, all individual door status variables across the canvas should immediately override to Forced Locked, ignoring local timer delays.

Currently, chaining After delay interactions inside nested component variants seems to drop variable evaluation when multiple door cards are updating simultaneously on the same board.

Has anyone found a reliable pattern for handling timer-based state rollbacks with conditional logic in Figma? Would it be cleaner to drive this through centralized string/boolean variable collections rather than nested component-level delay triggers?

1 reply

Emma Wingding
New Member
Oct 10, 2026 10:30 AM UTC

Hi Tekhabeeb — really cool use case! I've built a few timer-based prototypes with variables, and the pattern that worked reliably for me was to keep the timer logic out of the nested component variants entirely.

 

A few things I'd try:

 

1. Put the "After delay" logic on a top-level logic frame rather than inside the door card components. Interactions buried in nested instances are exactly where variable evaluation tends to drop — I hit the same thing on a multi-card prototype once. Let the cards just bind their visuals (variant properties driven by the variables) and keep all the sequencing in one place.

 

2. For the 3-second rollback, chain it like this on the "Simulate Access Granted" click: Set variable doorStatus = "Unlocked / Door Open", then "After delay 3000ms" → Conditional: if lockdown == true → set doorStatus = "Forced Locked"; else if holdOpen == false → set doorStatus = "Idle (Secured)". The trick is checking lockdown inside the delayed branch, since you can't cancel an "After delay" once it fires — if the operator hits lockdown during those 3 seconds, the delayed action re-checks the flag and applies "Forced Locked" instead of bouncing back to Idle.

 

3. For the global lockdown override, have the lockdown button set the lockdown boolean to true AND set each door's doorStatus variable to "Forced Locked" in the same click chain. Then any pending 3-second timer that fires later hits the conditional in step 2 and keeps the door locked. Lifting lockdown does the reverse: set lockdown = false and restore the statuses.

 

One boolean for the "Hold Open" toggle (per door, or a single global one if the toggle is global) plus a string variable for doorStatus per door kept things manageable for me. With hundreds of doors, obviously only a representative handful need to be live in the usability prototype — the pattern scales, and it keeps the file from getting too heavy.

 

Hope that helps — happy to dig into the conditional setup if you hit snags!