Glue Workflow Detail page fails to load
0
While trying to visualize the Glue Workflow detail page I get the following error:
There was an issue processing your request.
Error: ChunkLoadError: Loading chunk 7 failed. (error: https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/RouteBlueprintDetailPage~RouteMLTransformDetailsPage~RouteWorkflowDetailPage.js)
Info: a@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:13628 div V@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:518018 a@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:13628 E@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:4401 U@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:6709 a@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:13628 E@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:4401 E@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:4401 U@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:6709 a@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:13628 E@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:4401 Fa@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:558642 Suspense div div div me<@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:101:199190 div main div div yt<@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:101:239851 div ft<@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:101:237316 Se@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:429072 t@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:36:1332351 b@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:458196 L@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:419919 g@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:443253 M@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:420719 t.PreferencesContextProvider@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:34:63317 G@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:23:6830 s@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:36:760824 l@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:36:787259 t@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/vendors.js:82:591991 div ye a@https://a.b.cdn.console.awsstatic.com/a/v1/WVIDCGUOYOBAQRUEMPOEEI64KGOHRBJ5NASSIAI53VH6A3DDBSMQ/main.js:1:13628 Te
I am on a basic plan and cannot open a ticket. Anyone is experimenting the same issue?
demandé il y a 2 mois182 vues
1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
It may sound silly but... are you reloading this stuff ? Sometimes it's just that the server is not ready to process your requests for some unknown reasons... In general, errors related to failing to load page resources or connect to backend services indicate a temporary outage issue rather than an account-specific problem. Check the health status page.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a 7 mois
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 3 ans
Well ... yes I reloaded. I cleared the session etc... The issue persists and I cannot send a bug trace to AWS. The fact that you need to pay money for sending a bug to AWS has always sounded wrong to me. And it still sounds as wrong after 10 years :)