1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
We are seeing a similar issue on our end. We haven't made any changes to our application config, etc. Our scheduler is still submitting jobs to the application but after some time, we get a: Application Artifact Response is empty for customerId: xxx and applicationId: xxxx
Presumably this is due to the application staying in the "starting" state while jobs are being submitted.
con risposta 2 anni fa
It seems to be working now...
yup, it started working on its own. Would be good to have AWS acknowledge an outage for the service though
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 5 mesi fa
Problem happens in us-east-1 region, it is not reproducible in us-east-2 region.