Stand in front of the temporal anomaly before trying to interact. The required approach position is an intended mechanic, so a failed attempt from another side does not by itself mean the anomaly is broken.
The confirmed instruction is about where your character stands. It does not provide a special input combination, a hidden item requirement, or a universal distance measurement. Start by correcting your approach rather than adding an unverified step to the puzzle.
Change your position before retrying
- Stop repeating the interaction from the same unsuccessful position.
- Move around to the front of the temporal anomaly.
- Face it from that front position and try the interaction again.
Describe your position clearly to your partner. In a game where the two players often have different information, saying only that the anomaly does not work leaves out the part you can change immediately: your approach side.
The front requirement is the confirmed point. There is no verified compass direction, marked floor location, or exact number of steps that applies to every anomaly. Use the anomaly you are actually facing rather than expecting every encounter to share one room layout.
Recognize the limit of the position check
If moving to the front allows the interaction, you have addressed the documented requirement. A side or rear attempt was not evidence that you needed to reload the session.
If you are already at the front and interaction still fails, the position requirement alone does not explain the remaining problem. Do not assume that a second unseen activation condition, a specific tool, or a partner-only action is required without checking the current puzzle's actual information.
For a genuine progression block that persists, the general recovery route is main menu → Change → Start New Journey, followed by the host manually re-selecting your last checkpoint. This is a fallback for a blocked session, not the normal activation method for a temporal anomaly.
Keep the distinction clear on a retry: stand in front first; use checkpoint recovery only when you need to recover from a persistent block. There is no confirmed anomaly-specific patch or extra unlock described here.