[Bug]: Flow "write to a conversation" broken.

[schiessle]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I tried to setup a flow to write to a talk room whenever a file in a certain folder gets added/edited.

Steps to reproduce

1. tried in c.nc.com
2. setup this flow:

Expected behavior

I can setup the flow but instead I get the error you see on the screenshot

Nextcloud Server version

30

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Browser log:

{"ocs":{"meta":{"status":"failure","statuscode":400,"message":"Cannot decode operation details"},"data":[]}}

Additional info

No response

[RTechSn]

I confirm.

[RTechSn]

Here's some error from JS console:

```

store.js:42 TypeError: Cannot read properties of null (reading 'proxy')
at w (useModelMigration-EhAWvqDD.mjs:3:33)
at setup (NcSelect-DvGJHzaa.mjs:389:19)
at hn (vue.runtime.esm.js:3033:30)
at vue.runtime.esm.js:2457:27
at vue.runtime.esm.js:5385:5
at e._init (vue.runtime.esm.js:5714:9)
at new o (vue.runtime.esm.js:5849:18)
at vue.runtime.esm.js:4564:12
at init (vue.runtime.esm.js:4426:52)
at vue.runtime.esm.js:6591:17

store.js:107

POST https://nextcloud.....com/ocs/v2.php/apps/workflowengine/api/v1/workflows/user?format=json 400 (Bad Request)
(anonymous) @ xhr.js:195
xhr @ xhr.js:15
p @ dispatchRequest.js:51
_request @ Axios.js:173
request @ Axios.js:40
(anonymous) @ Axios.js:212
(anonymous) @ bind.js:5
pushUpdateRule @ store.js:107
await in pushUpdateRule (async)
(anonymous) @ vuex.esm.js:851
f.dispatch @ vuex.esm.js:516
dispatch @ vuex.esm.js:406
saveRule @ Rule.vue:149
hn @ vue.runtime.esm.js:3033
n @ vue.runtime.esm.js:1832
hn @ vue.runtime.esm.js:3033
e.$emit @ vue.runtime.esm.js:3732
click @ NcButton.mjs:232
hn @ vue.runtime.esm.js:3033
n @ vue.runtime.esm.js:1832
Pr.i._wrapper @ vue.runtime.esm.js:7500
Show 18 more frames
Show less
Rule.vue:154 Failed to save operation

</details>

[schmees-uol]

I can confirm this bug, too. Same console output (400, Bad Request).

[Antreesy]

This affects any workflows. Probably caused by nextcloud-libraries/nextcloud-vue#6172, as passed components can not grasp Vue instance of parent, therefore getCurrentInstance returns null.

Maybe it could be fixed in https://github.com/nextcloud/server/blob/f21ffabe0e92c1790262c07d51eb2a60f55796f2/apps/workflowengine/src/workflowengine.js ? cc @ShGKme @susnux

[blizzz]

And so also related to nextcloud-libraries/nextcloud-vue#6360 (i.e. yes, needs a fix in the workflowengine)