I'll go with B and D. Although, now I'm wondering if the backend team was just having a bad day and decided to 'accidentally' return a different response. Gotta love those passive-aggressive developers!
I'm going with B and D too. It's either a change on the service side or a change in the response. Can't be that the service went down, that would just return an error, not flush the cache.
B and D seem like the most likely options here. If the WSDL resource was updated, that could invalidate the cached result. And if the backend service returned a different response, that would also flush the cache.
Nadine
3 months agoJettie
3 months agoKimberely
3 months agoDeandrea
3 months agoMaia
4 months agoBonita
4 months agoLeslie
4 months agoKimbery
4 months agoOtis
3 months agoShanda
4 months agoDarnell
4 months agoElly
4 months agoDenny
3 months agoRolland
3 months agoSol
4 months agoNettie
4 months agoCyril
4 months agoLaticia
4 months agoCaprice
4 months agoJanella
4 months ago