> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-hk/faq/attendance-check-in/how-to-handle-position-abnormal-when-clocking-in.md).

# \[考勤打卡] 打卡出現定位異常應如何處理？

Wi-FI打卡：

可點選頁面內＂檢查異常＂，頁面會顯示錯誤詳情，包括設備當前連接上的Wi-Fi名稱及MAC地址。

查看系統後台打卡設置中的 Wi-Fi 名稱及 BSSID，以確認是否由於未連接合適的 Wi-Fi 或系統輸入的 BSSID 有遺漏或 Wi-Fi 名稱不正確而引致定位異常或有機會變成外勤打卡（如外勤打卡功能已開啟）。

GPS打卡：

系統會根據手機用戶當刻GPS的數據而判定是否為有效打卡。而每部手機GPS的信號都會因為不同物件／環境 （牆身厚道，其他信號發射器）影響強弱，因此為確保閣下公司所有員工能正常打卡，請設置打卡範圍為50米或以上。

詳情可點選頁面內＂檢查異常＂，頁面會顯示你的GPS定位位置與考勤位置相差多少米。可視乎地點信號受影響情況，嘗試擴大打卡範圍。

如果位置始終不正確，建議使用 Wi-Fi 打卡。


---

# 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://docs.coreway.com/coreway-hr/zh-hk/faq/attendance-check-in/how-to-handle-position-abnormal-when-clocking-in.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.