"after-script:" is not triggered pipeline errors when processing artifacts

https://bitbucket.org/pryoninc/api-tests-go/addon/pipelines/home?utm_term=pipeline&utm_source=bb-slack&utm_medium=referral-external&atlOrigin=eyJpIjoiMWRiZjlmZjhkYmE3NDg0Mzk3NWI3ODZhZjczNGQyODQiLCJwIjoiYmItY2hhdHMtaW50ZWdyYXRpb24ifQ#!/results/4702

Hi,

I understood that you had an incident yesterday that caused pipelines to fail to create an artifact.

https://bitbucket.status.atlassian.com/incidents/cqdkw0ywy34q

What I am asking here is that, in the situation that your pipelines steps failed internally (in this case “artifacts“ failed), could you please ensure that “after-script:” still triggered so that we have a chance to clean up our expensive resources.

Please let me know if you have any question.