Application where a chain of responsibility is better than a list of handlers

I am not quite sure when I would rather use a "true" chain of responsibility instead of a simple list of handlers. By true chain of responsibility I mean that every handler owns a link to the next handler.

Do you have some real world examples for it in backend or frontend programming? I can quite get my head around examples where you would use a chain of responsibility in production.

I know that servlet filters, c# middleware, some gui-libraries and logging libraries use a CoR. But I am looking for a problem that should be solved using a custom chain of responsibility in the actual backend/frontend logic.