Stuck Objectives: Prerequisite or Bug?

Your companion is beside you, the objective marker is ahead, and Aniimo's crowded menus have sent you through three screens without explaining why nothing counts. Open the active objective's details first. Read its completion requirement before trying the action again: recording a video, catching a creature, and using its ability are separate tasks.

Work through the checks below in order. The goal is to find the missing step—or narrow down an unresponsive action—so you can get back to exploring Idyll through your favorite companion's abilities.

Check the objective before repeating the action

1. Read the active objective and its displayed completion requirement. Note the target's name, the required action, and any progress count shown. Follow that objective's marker. After each attempt, check whether the wording or count changes; a nearby creature or completed animation alone does not show that the task counted.
2. Choose the recording or catching branch. If the task asks you to record a video of an Aniimo, follow the displayed camera recording prompt for the named creature. Check for recording completion and an objective update. If it asks you to catch one, enter Catch Mode and use an Aniipod, the device used to capture creatures. Wait for the catch result, then check the objective again. Recording a video does not replace a catch, and throwing a pod does not mean the catch succeeded.
3. Choose the command or Twining branch. A companion command tells your Aniimo to act while you remain your Pathfinder character. Twining lets you become a collected Aniimo and control it directly. Check the required ability against the selected companion's abilities. For a command prompt, follow the displayed companion action. For a Twine prompt, select the required companion, use the displayed Twine action, and read the changed skill prompts before acting.
4. Check for a missing prerequisite. Read any locked-action message or listed requirement. If the required ability or feature is unavailable, follow its displayed unlock requirement before returning. For a blocked route, check whether your selected Aniimo has the needed movement ability. For a missing wild target, check any listed habitat, weather, or time conditions. A suitable habitat is a search area, not a guaranteed spawn.
5. Test an unresponsive input separately. If the requirement is met and the action is available, close open menus, face the intended target, and check the current prompt. Follow its tap or hold instruction on your device. Make one attempt and watch for an animation, changed skill prompts, or an objective update. If a swap is delayed, wait until the selected Aniimo and its prompts match before using the skill. If a skill stops when you switch, retry without switching during that action. These checks help isolate the symptom; they do not establish its technical cause.
6. Update, then retry the same requirement. Install available updates through your usual launcher or storefront, and restart the client to download updated resources. Return to the objective and repeat the required action once, checking its completion text afterward. Compare your exact symptom with the dated fixes below. If it still stalls, record the quest name, objective wording, platform, build number, selected Aniimo, and what happens when you use the displayed action for a support ticket.

Prerequisite check: A message that names an unmet requirement gives you a next task. An available action that produces no response needs a separate input check. Repeating the button cannot unlock a missing ability.

Dated fixes: match the specific symptom

These builds corrected particular blockers. A similar-looking stall can have a different cause, so a historical fix is not a guaranteed remedy for your current objective. Dates below are the update announcement dates in UTC.

Tip: If teleporting leaves you in an incorrectly loaded scene, the September 30 build gives a specific recovery route: go to the Outpost and use the green interaction point to reload the correct scene. Use this for a scene-loading problem, then check your active objective again.