This question is more tricky that it appears at first. There is no easy place to check this. Timeout date for each Work Incident task is calculated just before starting task itself. This timeout date is not shown anywhere in the Portal and while it can be found in the database, querying the value needs a bit of doing.
Timeout date for a task is saved as a trigger date in properties of the associated message in the database. Querying that is not too bad and can be done with a query like this:
Here comes the problem - timeout date format there is .NET ticks. To get this date to a readable and usable datetime format, adding a function to the database is the easiest way:
After this function is added to the database, the timeout value can be converted to datetime in the query which will both give a readable date as well as enable some calculations to make it easier to find what we are looking for. Here is the query from above with two additional columns - timeout date in a readable format and calculated difference between the time task was started and timeout date in days. The last column should be the needed value:
You can add to the WHERE clause of the last query to filter out the Incidents where timeout is less than 365 days, for example by adding this to the end of WHERE clause to filter results to only Incidents with timeout time less than 370 days: