Entry Route Issues
Problems around QR handoff, route choice, and customer start-flow confusion.
Check charge hub path
Validate static route
Confirm the right flow for the site
This page organizes the public troubleshooting surface so the team can move from issue type to the relevant product route quickly. It complements the platform's session-linked logging approach.
Problems around QR handoff, route choice, and customer start-flow confusion.
Check charge hub path
Validate static route
Confirm the right flow for the site
Problems where charging starts, stalls, or diverges from expected lifecycle behavior.
Open live session route
Read state progression
Confirm remote action context
Problems where support needs more proof before deciding whether the issue is charger, payment, or process.
Use session-linked evidence
Read charger-specific traces
Keep support and finance context together
These route links are useful during review, demos, and early support rehearsals while the backend remains unchanged.
/charge
Use for route selection and customer-entry troubleshooting.
/static/[chargerId]
Use for QR-led, property-style, touchless flow review.
/charging/[sessionId]
Use for charging-in-progress support and state reading.
/status/[sessionId]
Use for end-state review and support handoff summaries.