I am adding timeouts to jobs, to prevent a problem with jobs that don't finish.

What I have observed is that when I placed a timeout at the job level, even with "treat timeout as error" selected, the job exits with no failure, hence I don't get a failure notification. It's important to get a failure notification if a job doesn't complete all of the tasks successfully. In this case, I am also using this in conjunction with a condition with a "retry" on a condition, (i.e. for a file copy, so that it doesn't fail if the network is temporarily unavailable), so there isn't a task that is running long enough to use the time out with.

Is there a way to set up the job so that I can get a notification if the timeout limit is reached?

I tested this as well. I setup a job with a timeout and consider timeout as error checked. The timeout is less than the normal job time, so it has to end the job before doing all tasks. If I put an error notification on this job, it's not fired. This should be the case I think.
I tested this with the current beta 4.9.11

---

This is fixed for the next release. Thanks for the report.

---