Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Di 30.07.2024 00:00:09 274.823 +9 5.703.994 20,8 mastodon.cloud 4.1.18 500 Mo 29.07.2024 00:00:38 274.814 +12 5.702.172 20,7 mastodon.cloud 4.1.18 500 So 28.07.2024 00:00:07 274.802 +18 5.700.930 20,7 mastodon.cloud 4.1.18 500 Sa 27.07.2024 00:00:09 274.784 +8 5.699.636 20,7 mastodon.cloud 4.1.18 500 Fr 26.07.2024 00:01:07 274.776 +10 5.697.668 20,7 mastodon.cloud 4.1.18 500 Do 25.07.2024 00:00:10 274.766 +9 5.695.805 20,7 mastodon.cloud 4.1.18 500 Mi 24.07.2024 00:00:00 274.757 +12 5.694.383 20,7 mastodon.cloud 4.1.18 500 Di 23.07.2024 00:01:00 274.745 +11 5.692.740 20,7 mastodon.cloud 4.1.18 500 Mo 22.07.2024 00:01:11 274.734 +5 5.691.059 20,7 mastodon.cloud 4.1.18 500 So 21.07.2024 00:00:59 274.729 0 5.689.566 20,7 mastodon.cloud 4.1.18 500
Benjamin Smedberg (@bsmedberg) · 11/2022 · Tröts: 217 · Folger: 46
Di 30.07.2024 22:26
TIL: some errors in auth0 login flows will show the user a message "There could be a misconfiguration in the system or a service outage. We track these errors automatically, but if the problem persists feel free to contact us with this tracking id: XXXXXXXXXXXXXX. Please try again."
And not only can you as auth0 customer not search the logs for this tracking ID... even auth0 tier-1 support personnel can't. Only their escalation devs can, so they try to fix issues without logs.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0