Task: Reduce requests for requests with error response

[n3rdc4ptn]

Understand the Task

Description
When requests get back with errors (e.g. 404) we should not fetch them as often as our other requests.
Either not do a new requests at all and instead show the user a manual refresh button.
OR
Reduce the amount of requests if the request last time responded with an error.

Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

• Failing requests should not be refetched as often as normal requests
• separate interval for failing requests

[GenosseOtt]

TODO: add to dev sync? Circuit breaker pattern? @enrico-kaack-comp

[andreaskienle]

With GraphQL, we'll need to adjust our data-fetching. We'll also have new options like subscriptions which could replace polling in some cases. How about we revisit this topic once GraphQL is fully implemented?

[n3rdc4ptn]

With GraphQL, we'll need to adjust our data-fetching. We'll also have new options like subscriptions which could replace polling in some cases. How about we revisit this topic once GraphQL is fully implemented?

I agree, lets postpone that. Otherwise we would do that discussion again with GraphQL