1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a un an
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
Contenus pertinents
- demandé il y a un an
- demandé il y a 5 jours
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
Problem happens in us-east-1 region, it is not reproducible in us-east-2 region.