Comment 20 for bug 1982804

So looks like the application didn't get updated in time after the images were refreshed in AMS. It depends on the number of applications created in AMS and the free resources that your deployment owns to schedule a base container for an application update. Usually, after the parent images got updated(in your case, 1.14.x -> 1.15.0), AMS will schedule an update for each application and a new revision of the application will be generated automatically afterward.

Anyway, it's good to hear it's working fine now.