> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/4.-developer-and-payment-engine/waas/callback-query.md).
# Callback Query
In daily operation, if the business callback fails due to abnormal factors such as changes in the callback address of the business platform and unstable network, and the order status is not updated, it can be viewed and processed in the project callback record.
1. Click "API" in the Cregis client - > "History Callback" to display abnormal callback records by default. If the data is empty, it means that there is no abnormal callback data in the current project.
2. If there is an abnormal callback that causes the order status of the business platform to not be timely updated, click the "Feed" button.
3. If the callback fails due to a change in the callback address, please enter the correct callback address and enter the Google 2FA code for verification.
---
# 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://support.cregis.com/4.-developer-and-payment-engine/waas/callback-query.md?ask=&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.
