Scheduled jobs that end up with error because their running time is over the specified timeout threshold for said job are not triggering a "failed notification". This used to work in AWX 8.0.0.
Create some notifications in an AWX instance. I'm my case I'm trying with "email" and "Slack" notification types.
Create or modify an AWX job and set the following:
Run the job and be sure to make it fail due to timeout.
Verify that no "failure notification" is triggered.
A "failure" notification should be triggered. This is the behavior that AWX 8.0.0 used to have.
No notification is triggered and the job fails silently.
Screenshot of a failed job reporting a timeout error:

The notification configuration for the failed job:

The failing job configuration used to reproduce the issue. Please note that the low timeout is there just for demonstration purposes. The original failing job has a timeout of 3600s.

1) Created slack notification
2) Created Job template with a playbook that takes 30 seconds and a time out of 5 seconds (so it would fail with timeout)
3) Created schedule to launch job every minute
4) Associated notification w/ job and enabled it for failures (to get notification when jobs failed)
5) Waited and observed that job did lauch, failed, and I got notification
Most helpful comment
1) Created slack notification
2) Created Job template with a playbook that takes 30 seconds and a time out of 5 seconds (so it would fail with timeout)
3) Created schedule to launch job every minute
4) Associated notification w/ job and enabled it for failures (to get notification when jobs failed)
5) Waited and observed that job did lauch, failed, and I got notification