1 Answer
- Newest
- Most votes
- Most comments
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.
answered 2 years ago
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
Relevant content
- asked 2 years ago
- asked 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
Problem happens in us-east-1 region, it is not reproducible in us-east-2 region.