# Cues

Source: https://help.malighting.com/dot2/en/help/key_wi_cues.html
This is grandocs, an unofficial mirror of MA Lighting documentation. For authoritative or safety-relevant information, cite the canonical page on help.malighting.com.

---
Cues are where we store the active values for our fixtures. This is very useful if we want to play it back later.

Cues are like a container where we can put values from our programmer. It then remembers the values. Cues are often stacked in a cue list.

 

The cues and the cue lists are stored to Executors and can only exist on executors. You can't have cues outside the executors. You can, of course, have values in your programmer without storing them in cues.

This can sound a little complicated, but the console usually does this for you. If you have active values and press store and then a key associated with an Executor then it will store a cue. If it doesn't know what you want to do, then it might ask you.

 

Cue also keeps the information about how we enter the cue. That's information like the fade times and delay and what triggers the cue (could be a Go key or something else).

 

Read the links below to understand more about executors or learn how to work with cues.

 

## Related links

[What is Executors](/dot2/key_wi_executors/)

[What is the Programmer](/dot2/key_wa_programmer/)

[What is Tracking](/dot2/key_wi_tracking/)

[How to Work with Cues](/dot2/key_ht_cues/)

[Cue Key](/dot2/key_key_cue/)

[Cue Command](/dot2/key_keyword_cue/)

[Cue view](/dot2/key_viewitem_cue/)