What the data for this category looks like
Multi-app routing data primarily comes from three sources within the platform: configured sub-app metadata, traffic allocation rules, and session pass-through configurations. Data updates are triggered on demand, and sync when sub-apps go online or offline, traffic rules are adjusted, or session pass-through fields are modified. The document structure of a single routing data entry includes the unique route identifier, bound sub-app ID list, traffic allocation ratio array, session pass-through field set, and permission scope configuration.
route_id is a string type. app_ids is a string array. traffic_split is a numeric array. The unit of session_expire is seconds.
What constraints these characteristics impose on sharing and embedding workflows
Multi-app routing binds multiple sets of sub-app metadata. For this reason, sharing and embedding steps must pass the unique route identifier. Do not use a single sub-app ID, as this will not trigger the preset traffic allocation logic.
Session pass-through fields require the embedding code to carry corresponding parameters. Without these parameters, context loss will occur during cross-sub-app session handoff.
Traffic allocation rules update dynamically. Embedding configurations cannot hardcode sub-apps. They must always bind the route identifier to adapt to rule changes.
Permission scope configuration limits the access boundary of sharing and embedding. The permission settings for login-free pages must match the permission scope defined in the route configuration. Otherwise, access will be blocked.
Session expiration time configuration directly affects the valid duration of embedded sessions. It must match the session cycle of the target business scenario.
How to set configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
route_id | Unique route identifier string generated by the platform | Bind to the target route configuration to ensure normal triggering of traffic allocation and session pass-through logic |
enable_session_pass | true (cross-app session scenario) or false (single-app temporary scenario) | When enabled, session context can be passed to all bound sub-apps to avoid context loss |
share_expire_time | 3600 seconds (adjust based on business scenario) | Controls the valid duration of shared links, matches the business session cycle |
force_language | zh-CN, en, or set based on actual testing | Unify the display language of the embedded page to avoid multi-language adaptation deviations |
disable_voice_input | false (enable as needed) | Controls the voice input function of the login-free page, adapts to the interaction requirements of the business scenario |
The parameter values provided on this page are all conventional recommendations used as starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Symptom: After embedding, multi-app traffic allocation cannot be triggered, and only jumps to a single sub-app. Cause: The embedding code uses a sub-app ID instead of
route_idas the binding parameter, and fails to correctly associate the route configuration. - Symptom: Voice input on the login-free page is unresponsive or the time display shows 00:00. Cause: The
disable_voice_inputparameter is not configured correctly, or the embedding code does not carry verification parameters related to route permissions, resulting in the voice input function being blocked. - Symptom: Cross-sub-app session context is lost, and conversation logic cannot be continued. Cause: The
enable_session_passparameter is not enabled, or the embedding code does not pass session pass-through fields, resulting in context unable to flow between sub-apps.
How to confirm the configuration is correct
- Open the embedded page, check if the route parameter in the address bar contains
route_id, confirm that it is bound to the target route configuration. - Initiate a cross-sub-app conversation, check if the session context continues normally between different sub-apps, confirm that the
enable_session_passconfiguration takes effect. - Adjust the
force_languageparameter and refresh the page, check if the page display language matches the preset value, confirm that the language configuration takes effect. - Test the voice input function, check if it can trigger normally and display the input duration, confirm that the voice input configuration meets business requirements.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.