# After\_success or deploy still run after script failed

**URL:** <https://travis-ci.community/t/after-success-or-deploy-still-run-after-script-failed/13787>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [April 26, 2023, 1:13am UTC](https://travis-ci.community/t/after-success-or-deploy-still-run-after-script-failed/13787 "2023-04-26T01:13:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wrao](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@wrao](https://travis-ci.community/u/wrao)\
**Post date:** [April 26, 2023, 1:13am UTC](https://travis-ci.community/t/after-success-or-deploy-still-run-after-script-failed/13787/1 "2023-04-26T01:13:03Z")

</div>

I saw this happen recently. My build failed on script, but the deploy or after\_success still run. Is this expected?

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [April 27, 2023, 3:11pm UTC](https://travis-ci.community/t/after-success-or-deploy-still-run-after-script-failed/13787/2 "2023-04-27T15:11:15Z")

</div>

Please reference this post where I post a workaround:

> [@The travis job terminated successfully, but after\_failure is called](https://travis-ci.community/t/the-travis-job-terminated-successfully-but-after-failure-is-called/13727/2):
>
> We’re also seeing this same exact issue - it started around 6AM Eastern on March 28, 2023. With no changes to our scripts or travis.yml, all f our jobs returned 0 and ran the after\_failure: The command "INSTALL\_MODE="install" ./canary-scripts/deploy.sh" exited with 0. $ ./canary-scripts/failure.sh We’ve reached out to Travis Support!