For Dynamic Mapper , Subscription outbound mapping in not working

Forum
,
1

I am using Cumulocity frontend 1018.0.233 and backend 1018.0.356
i have tried two versions of dynamic mapper 4.3 and 4.5.3 and both I have faced same issue
the issue is during the outbound mapping.
asI have tried to add devices on the Subscription outbound mapping it gives an error and below screenshot from inspect

image
image1154×296 15.2 KB

and
I have checked Notification 2 permission and it was enabled

and below logs from Dynamic mapper microservice
2025-04-23 11:35:52.925 ERROR 11 — [p-nio-80-exec-9] d.m.r.DeviceSubscriptionRestController : Tenant t19885 - Error updating subscriptions:

com.cumulocity.sdk.client.SDKException: Http status code: 404
tenant: t19885 user: service_dynamic-mapping-service
at com.cumulocity.sdk.client.ResponseParser.checkStatus(ResponseParser.java:81)
at com.cumulocity.sdk.client.ResponseParser.parse(ResponseParser.java:63)
at com.cumulocity.sdk.client.RestConnector.get(RestConnector.java:118)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:130)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:125)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:116)
at dynamic.mapping.notification.C8YNotificationSubscriber.lambda$getDeviceSubscriptions$7(C8YNotificationSubscriber.java:399)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.lambda$runForTenant$7(MicroserviceSubscriptionsServiceImpl.java:242)
at com.cumulocity.microservice.context.ContextServiceImpl.callWithinContext(ContextServiceImpl.java:78)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.lambda$callForTenant$8(MicroserviceSubscriptionsServiceImpl.java:251)

2

Can you verify that notification 2.0 is working in your tenant?

It seems notification 2.0 is not working properly at your tenant because 404 is returned when accessing the API of it to retrieve & updating the device subscriptions.

Also with the standalone app you are not bound to any dynamic mapper release anymore, so you can also try the latest 5.0.0 release which contains a lot of improvements and bug fixes but I doubt it will resolve your issue as it seems to be related to your instance/tenant.

Update:
I see you tagged “edge”. For edge notification 2.0 isn’t available yet so you have to disable outbound mappings in the service configuration.

3

hello Stefan, the Notification 2 is enabled as per below screenshot

image
image1644×787 39.4 KB

and regarding edge , the tag was added by mistake. our platform is not edge
and regarding the release 5.0.0, I am not able to install it with our tenant version 1018