WayaDesk / Operations and recovery
An expired label and an observed session can disagree for several reasons. Investigate the account, the access path and the freshness of the observation before changing billing records to make the display consistent.
Confirm the expected boundary
Read the actual paid-through time and timezone. Check whether a future period was purchased or a deliberate adjustment was recorded. Do not rely only on what staff remember from the original package sale.
Establish which access is being used
The customer may be connecting through a different credential, another network path or a session observation that is no longer current. Match the subscriber, router and relevant timestamps before concluding that expiry enforcement failed.
- Verify the expected service boundary against the account history.
- Inspect current router or accounting evidence.
- Test the reconnect result with a controlled expired account.
Preserve evidence while correcting
Avoid deleting the original transaction or granting a new period merely to clear an inconsistency. If an enforcement action failed, use the supported diagnostic and recovery process and record the result. Intentional operator exceptions should remain distinguishable from accidental continued access.
Retest the specific path
A local Hotspot expiry result does not validate RADIUS PPPoE, and the reverse is also true. Repeat acceptance for the actual path involved. This helps identify a service-specific gap instead of incorrectly changing every package in the catalogue.
Frequently asked questions
Does an old active-session row prove current access?
No. Check its freshness and observe the actual connection.
Should staff extend expiry to match the session?
Not as a diagnostic shortcut. Establish the cause and preserve the original entitlement evidence.
Choose your software licence
One installation, a clear router allowance, and perpetual use of the purchased version. Setup assistance, hosting and external services are separate.