# Fail to config Cumulocity IoT Trigger In WM.io workflow **URL:** \ **Category:** Forum\ **Tags:** cumulocity\ **Created:** [March 3, 2023, 6:45am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012 "2023-03-03T06:45:41Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![anon18601492](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@anon18601492](https://community.cumulocity.com/u/anon18601492)\ **Post date:** [March 3, 2023, 6:45am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/1 "2023-03-03T06:45:41Z")
#### Dear Team I am working for a demo that integrating Cumulcity alarm into Kafka . In the workflow definition, system throw error message **‘An unexpected error occurred during the creation of the Cumulocity IoT service user’**. I have check the privilege for the user of Cumulocity Connect, he/she is ‘Admin’ and with ‘Notification 2’ privilege. My Coumuloity is **1015.0.278**. ---
**Author:** ![anon18601492](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@anon18601492](https://community.cumulocity.com/u/anon18601492)\ **Post date:** [March 3, 2023, 6:46am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/2 "2023-03-03T06:46:00Z")
![wm_error](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/4/b/4b8f50b7c03d8cc069077e35a2d2097c206ce4eb.png) ---
**Author:** ![Michael\_Voigt2](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/michael_voigt2/32/18431_2.png) [@Michael\_Voigt2](https://community.cumulocity.com/u/Michael_Voigt2)\ **Post date:** [March 3, 2023, 7:10am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/3 "2023-03-03T07:10:37Z")
The user that you use to create the connection with needs to have ADMIN permissions for “Application management”. But it seems the connection “WmC8YCoreConnect\_SmartFacility” is properly created as you selected it in the screenshot. So the error is coming when you try to save (or run?) the workflow? Which [wm.io](http://wm.io) instance are you using? Thanks, Michael ---
**Author:** ![anon18601492](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@anon18601492](https://community.cumulocity.com/u/anon18601492)\ **Post date:** [March 3, 2023, 7:35am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/4 "2023-03-03T07:35:01Z")
the domain for the [wm.io](http://wm.io) is **[asiasales.int-aws-us.webmethods.io](http://asiasales.int-aws-us.webmethods.io)** ---
**Author:** ![Robert\_Neale](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/robert_neale/32/31965_2.png) [@Robert\_Neale](https://community.cumulocity.com/u/Robert_Neale)\ **Post date:** [March 3, 2023, 10:17am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/5 "2023-03-03T10:17:34Z")
There is a general problem at the moment that means cumulocity connectors are not created. A fix is waiting to be implemented in the AWS instance to fix this, but has not been done yet. ---
**Author:** ![Frederic\_Joulin1](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/frederic_joulin1/32/19452_2.png) [@Frederic\_Joulin1](https://community.cumulocity.com/u/Frederic_Joulin1)\ **Post date:** [March 3, 2023, 11:25am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/6 "2023-03-03T11:25:34Z")
Hello Weihan, Thank you very much for all the information. As far as I can see, your configuration meets all the requirements to be able to create a Cumulocity IoT alarm trigger. This error is actually caused by an issue in [webMethods.io](http://webMethods.io) tenants running on AWS datacenters. A correction will be rolled out with [webMethods.io](http://webMethods.io) 10.16. This new version should be deployed very soon although no actual date has been be scheduled so far. In the meantime you might try the following: - this issue started occurring upon creation in [webMethods.io](http://webMethods.io) of multiple Cumulocity IoT Accounts for different Cumulocity IoT tenants. It _might_ still work if you use the first Cumulocity IoT account you created - or at least an account on the same tenant. However, this solution does not work on all AWS tenants. - For demo purposes I would suggest to use a [webMethods.io](http://webMethods.io) tenant on an Azure datacenter. [webMethods.io](http://webMethods.io) V10.16 already runs on these tenants and the Cumulocity IoT trigger works as expected. ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/system/32/31990_2.png) [@system](https://community.cumulocity.com/u/system)\ **Post date:** [August 30, 2023, 11:26am UTC](https://community.cumulocity.com/t/fail-to-config-cumulocity-iot-trigger-in-wm-io-workflow/1012/7 "2023-08-30T11:26:29Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.