初始运行状况信息中心
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
初始运行状况信息中心
初始运行状况信息中心因环境而异,您可查看沙盒环境和生产环境中预订等候名单集成的当前运行状况。
在集成初期,沙盒环境信息中心会显示您已完成哪些集成以及哪些集成仍需要多加关注。为了顺利发布,您应在沙盒环境和生产环境中实现良好的集成。
访问初始运行状况信息中心
登录合作伙伴门户后,请选择“信息中心”下的“初始运行状况”链接。初始运行状况信息中心只能由端到端集成 v3 版本(即非候位名单、商家关联或重定向集成)上的合作伙伴使用。
在沙盒环境和生产环境信息中心之间切换
在合作门户中的沙盒环境和生产环境中均可查看初始运行状况信息中心。如需在生产环境和沙盒环境之间进行切换,请按照环境切换器文档中的说明进行操作。
每种状态的含义
每项初始健康检查旁都会显示三种不同的状态选项:
- 通过(绿色):您已通过此项检查。目前已满足所有条件。
- 失败(红色):目前未满足此集成健康检查的条件。这可能是因为您尚未开始处理集成的这一方面。
- 不适用(黄色):此初始健康检查不适用于您的集成。这可能是因为您的集成已停用特定功能。您无需担心这些检查。
需要满足哪些条件才能通过检查?
为了使您的预订等候名单集成被视为运行状况良好,您的每项检查均需显示“通过”(绿色)或“不适用”(黄色)。
每项不同的初始健康检查都会在页面右侧的检查旁列出相应的条件。相关条件取决于是否准确无误地成功上传了 Feed、预订服务器 API 响应以及实时的更新请求。
所需的尝试次数将因环境(生产环境与沙盒环境)以及路线而异(例如,与 CreateBooking 相比,您将需要针对 CheckAvailability/BatchAvailabilityLookup 进行更多的测试)。每项未通过的测试都会在得分旁边显示说明,告诉您不符合哪些条件。
此信息中心多久更新一次?
初始运行状况信息中心每两小时更新一次。对集成进行更改后,您将需要重新测试集成的该部分,并等待两小时以反映出相应更改。
例如,如果您更新了您的 CreateBooking 路线,则需要从 Action Center 前端测试该路线,并等待两小时以便信息中心反映出相应更改。
为何会显示未在初始运行状况信息中心实现的内容?
由于可以使用不同类型的集成,因此可能存在一些不适用于您的初始检查。如果特定检查不适用于您的预订等候名单集成,则将以黄色标记为“不适用”。
某些检查映射适用于各种集成类型。例如:
- BatchAvailabilityLookup 检查也适用于 CheckAvailability。
如果您不确定某项特定的初始健康检查的确切条件,则可以参考页面右侧的指南。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThe onboarding health dashboards monitor the status of your Reservations Waitlist integration in both sandbox and production environments, indicating areas that need attention.\u003c/p\u003e\n"],["\u003cp\u003eTo launch, your integration must be healthy in both sandbox and production, displaying "Pass" (Green) or "N/A" (Yellow) for all checks on the dashboard.\u003c/p\u003e\n"],["\u003cp\u003eYou can access the dashboards through the Partner Portal under "Dashboards" > "Onboarding Health" if you are on a v3 end-to-end integration.\u003c/p\u003e\n"],["\u003cp\u003eDashboard status indicators include "Pass" (Green) for meeting criteria, "Fail" (Red) for unmet criteria, and "N/A" (Yellow) for inapplicable checks.\u003c/p\u003e\n"],["\u003cp\u003eThe dashboards update every two hours, requiring re-testing and a waiting period for changes to be reflected after integration modifications.\u003c/p\u003e\n"]]],["The Onboarding Health dashboards display the status of your Reservations Waitlists integration in sandbox and production environments. Access them in the Partner Portal under \"Onboarding Health.\" Each check will display as Pass (green), Fail (red), or N/A (yellow). To launch, all checks must be Pass or N/A. Criteria for passing are listed next to each check and are based on feed uploads, booking server API responses, and real-time update requests. The dashboard updates every two hours.\n"],null,["# Onboarding Health Dashboards\n----------------------------\n\nThe onboarding health dashboards are environment specific and will allow you to\nsee the current health of your Reservations Waitlistsintegration in your sandbox and\nproduction environments.\n\nDuring onboarding, the sandbox dashboard will show you which areas of\nthe integration you have completed and which areas of the integration still need\nmore attention. In order to launch it is expected that you have a healthy\nintegration in both Sandbox and Production.\n\nAccessing the Onboarding Health Dashboards\n------------------------------------------\n\nOnce logged into the Partner Portal, select the \"Onboarding Health\" link under\n\"Dashboards.\" The onboarding health dashboards can only be used by partners on\nv3 of end-to-end integrations (ie not waitlist, business link, or redirect\nintegrations).\n\nSwitching between Sandbox and Production dashboards\n---------------------------------------------------\n\nThe Onboarding Health dashboard is available in both sandbox and production\nenvironments in the partner portal. To switch between production and sandbox\nplease follow the [environment switcher documentation](/actions-center/verticals/reservations/waitlists/partner-portal/overview/environment-switcher)\n\nWhat each status means\n----------------------\n\nThere are three different status options you will see next to each onboarding\nhealth check:\n\n- Pass (Green): You are currently passing this check. All criteria are currently being met.\n- Fail (Red): The integration is not currently passing the criteria for this integration health check. This could be because you have not begun working on this aspect of the integration yet.\n- N/A (Yellow): This onboarding health check does not apply to your integration.This could be because a specific feature has been turned off for your integration. You do not need to worry about these checks.\n\nWhat criteria do I need to meet to get a passing score?\n-------------------------------------------------------\n\nIn order for your Reservations Waitlists integration to be considered healthy, you\nwill need every check to say either Pass (Green) or N/A (Yellow).\n\nEach different onboarding health check will have the criteria listed next to\nthe check on the right of the page. The criteria are based off of successful\nand error free feed uploads, booking server api responses, and real-time update\nrequests.\n\nThe number of attempts needed will vary by environment (production vs\nsandbox) as well as the route (for example, you will need to make more tests for\nCheckAvailability/BatchAvailabilityLookup than you would\nneed to for CreateBooking). Each test that is not passing will\nhave a description next to the score telling you what criteria has not been met.\n\nHow often does this dashboard update?\n-------------------------------------\n\nThe onboarding health dashboards update once every two hours. After you make a\nchange to the integration you will need to re-test that portion of the\nintegration and wait two hours for the changes to reflect.\n\nFor example, if you update your CreateBooking route, you will need to test that\nroute from the Actions Center frontend and wait two hours for the changes to\nreflect on the dashboard.\n\nWhy are there things I did not implement on the onboarding health dashboard?\n----------------------------------------------------------------------------\n\nBecause there are different types of integrations available, there may be some\nonboarding health checks that do not apply to you. If a specific check does not\napply to your Reservations Waitlists integration, it will be marked as N/A in yellow.\nCertain checks map apply to a variety of integration types. For example:\n\n- The BatchAvailabilityLookup check also works for CheckAvailability.\n\nIf you are unsure of the exact criteria for a specific onboarding health check,\nyou can reference the guide on the right of the page."]]