You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue reported by a program admin on ccebikes where they were unable to view the user_token to user_id mapping.
They showed a screenshot and I observed that although the UUIDs tab was selected, the data being shown was the trips table, not the UUIDs table.
I tested it myself by logging in on production. The initial loading was extremely slow. The UUIDs table showed a loading indicator and never appeared even after several minutes.
I suspect that the program admin had previously viewed the Trips table, then switched to the UUIDs tab, but the request failed or eventually timed out. Then the Trips table showed because it was still in memory.
The text was updated successfully, but these errors were encountered:
The real problems is that the UUID table is timing out. Even if we fix the underlying issue (by showing a blank screen when we timeout), a timing out UUID table is a real problem for program admins that need to monitor their programs and potentially reach out to people to fix issues.
I hate to commit to doing any work because I am typically a bottleneck, but we don't have an army of interns any more, so let me try to see if I can squeeze in some improvements next week.
Issue reported by a program admin on
ccebikes
where they were unable to view theuser_token
touser_id
mapping.They showed a screenshot and I observed that although the UUIDs tab was selected, the data being shown was the trips table, not the UUIDs table.
I tested it myself by logging in on production. The initial loading was extremely slow. The UUIDs table showed a loading indicator and never appeared even after several minutes.
I suspect that the program admin had previously viewed the Trips table, then switched to the UUIDs tab, but the request failed or eventually timed out. Then the Trips table showed because it was still in memory.
The text was updated successfully, but these errors were encountered: