The request to /recordings/calendars (on scheduler service) take to long and some CAs run into timeout. This happen if you schedule 100+ Recordings for one CA. Other test scenario is to increase the query cutoff value of the CA (e.g. to two moth or more).
Steps to reproduce:
1. schedule multiple recordings
2. call /recordings/calenders?agentid=<CA-name>&cutoff=<date in ms since 1970-01-01>
Note if yu run the rest call with curl on linux terminal, you can set the cutoff value of +5 days with $(date -u -d '+5 days' +'%s')000 (note: three zeros at the end are important!)
With 100+ expected schedules in the calendar the request take 30+ seconds or more.