diff --git a/acceptance/bundle/apps/job_permissions/out.after_first_deploy.txt b/acceptance/bundle/apps/job_permissions/out.after_first_deploy.txt
deleted file mode 100644
index 27ba77ddaf6..00000000000
--- a/acceptance/bundle/apps/job_permissions/out.after_first_deploy.txt
+++ /dev/null
@@ -1 +0,0 @@
-true
diff --git a/acceptance/bundle/apps/job_permissions/output.txt b/acceptance/bundle/apps/job_permissions/output.txt
index ec50e4828c6..db0a6cafed3 100644
--- a/acceptance/bundle/apps/job_permissions/output.txt
+++ b/acceptance/bundle/apps/job_permissions/output.txt
@@ -15,9 +15,6 @@ Add the following section to the jobs permissions:
 
 
 
-=== After first deploy
->>> has_manage_run
-
 === After second deploy
 >>> [CLI] bundle deploy -qq
 Warning: app "my_app" references jobs "my_job" which has permissions set. To prevent permission override after deploying the app, please add the app service principal to the jobs permissions
diff --git a/acceptance/bundle/apps/job_permissions/script b/acceptance/bundle/apps/job_permissions/script
index 62b2886186b..191a5af55fe 100644
--- a/acceptance/bundle/apps/job_permissions/script
+++ b/acceptance/bundle/apps/job_permissions/script
@@ -12,8 +12,6 @@ has_manage_run() {
     | jq 'any(.access_control_list[].all_permissions[]; .permission_level == "CAN_MANAGE_RUN")'
 }
 
-title "After first deploy"
-trace has_manage_run > out.after_first_deploy.txt
 # This is flaky on direct, because there are (at least) two ways to complete deployment:
 # sequence 1:
 #  job is deployed
@@ -23,8 +21,6 @@ trace has_manage_run > out.after_first_deploy.txt
 #  job is deployed
 #  app is deployed, updates job permissions
 #  job permissions are deployed
-# (It does not appear flaky on TF, maybe there is enough delay in one of the resources)
-rm -f out.after_first_deploy.direct.txt
 
 title "After second deploy"
 trace $CLI bundle deploy -qq