Interactions to custom component stopped working

Question

I have created a beta site with 6 Page States. The last state has a custom component state that has 9 states of its own. The icon on Page 1 was clickable and transitioned to State 1 of Page 6, but when I linked the remaining 8 icons on Page 1 (for a total of 9) to their component states' variation; it stopped all transition to page 6 stopped. The transitions/interaction to Page 9 w/ custom components stop working. Is their a limit to the number of  these states? All other transitions to the remaining pages are working beautifully! This is a cool program. I almost completed a project without any help other than the videos.

Answer 1

Gotcha. There is no limit to the number of objects per state of a custom component, and there is no problem with having text and an image in the same custom component.
I think your explanation of states, transitions, and custom components might still be a little confused, so let me try to explain it a different way:
Your main application has a set of states, aka views or places the user can go. You can create transitions that play when the user goes from a state to another state - so there are two transitions for every pair of states (A -> B and B -> A). It also has a set of objects (aka layers) which you can see in the Layers panel. Some objects only exist in one state, while some objects appear in multiple states.
A custom component is like an enclosed microcosm of the main application. You can create states, and define transitions between pairs of states. You also define the set of objects in the custom component. These objects may exist in one or more states of the custom component, but are separate from the objects in the main application.
There's no such thing as a transition from a state of the custom component to a state of the main application, or vice versa. Each component (the main application and the custom component) has its own set of states and transitions between those states. Likewise, each component has its own set of layers, and cannot manipulate the layers of other components.
When you have an instance of a custom component in your main application, you can set its visibility, position, and other properties in each state of the main application, but you can't make changes to its layers between states of the main application. One property that you can change is its its state (either by creating an Interaction, or by creating a "Set Component State" action in a timeline). Setting its state will cause it to play the transition that exists from its current state to the new state, if such a transition exists.
Does that make sense?
-Adam