Problem

/schedules/{id} is in among the most queried endpoints, the response cache header is set with the default 1 second max-age. This can cause a lot of unnecessary queries sent to the backend when the schedule has already finalized (either executed or expired).

In order to reduce the load, a much longer max-age (e.g., 1 hour) should be used instead.

Solution

Set a longer max-age for /schedules/{id} response if any of the following is true

• deleted is true
• executed_timestamp is not null
• executed_timestamp is null, and one of the following is true
  • expiration_time is null and the wall clock time is at least 31 minutes after consensus_timestamp
  • expiration_time is not null and the wall clock time is at least 1 minute after expiration_time

Alternatives

No response