Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.4.3
-
Fix Version/s: 5.5.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
It's fixed for now, but it's not totally clear how to properly handle this kind of situation: maybe the component has the need for accessing these informations...
Maybe send async should be handled by the container instead of the CDK as discussed offline.