There was an ordering error in the conditions as well, causing the wrong async customizers to be registered. Another issue was the servlet async processing (request atribute not cached in all branches) resulting in multiple spans per request.
There was an ordering error in the conditions as well, causing the wrong async customizers to be registered. Another issue was the servlet async processing (request atribute not cached in all branches) resulting in multiple spans per request.