> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-hardware-specialists/scanners/troubleshooting/alterra-ikon-scanning-hydration-issue.md).

# Alterra/Ikon/Scanning/Hydration Issue

A guide to resolving guests that appear as just a pass number instead of a name in flaik

For resorts using Ikon passes (primarily Alterra resorts but potentially any resort that [Ikon passes are valid at](https://www.ikonpass.com/en/destinations)), they can experience an issue where the guest's pass number initially appears instead of the guest name.

### Summary

When scanning IKON Passes (which could impact Alterra and non-Alterra resorts) or any pass sold through Alterra's Central RTP environment (such as single mountain passes or employee passes, which would impact just Alterra resorts, the guest's name will not appear in flaik until after their first lift scan of the season and instead they'll be just listed as their pass number. 

{% hint style="info" %}
This is a season-level process, not a daily one.<br>
{% endhint %}

### What does this mean?

* When the pass is scanned in flaik before the guest has gone through a lift gate, the guest will appear only as their RFID number.
* Once the guest passes through a lift gate for the first time that season, the RFID is scanned and the guest record is "hydrated" into the local RTP environment.
* After the guest has been hydrated, flaik will continue checking the local RTP environment for up to three days and will automatically replace the RFID number with the guest's actual name.
* So, if an instructor scans an IKON Pass before the guest has scanned through a lift gate for the first time that season, seeing only the RFID number is expected behavior.
* Times where this becomes a little more complicated is when a guest is a beginner and may not have the opportunity to pass through a gate until they actually go up a lift (eg the resort doesn't typically scan for their magic carpets).
* That said some resorts scan passes at carpets and other beginner areas for other reasons on low volume days, so hand scanners for lift access is also a way that the guest name will hydrate into local RTP environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-hardware-specialists/scanners/troubleshooting/alterra-ikon-scanning-hydration-issue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.