"The provided flow name '<null>' is not valid." when posting a Teams feed notification

(33) Share

Report

Posted on by inserve

This flow worked already for months, and suddenly stopped working with the error "The provided flow name '<null>' is not valid." I see no option to specify the 'flow name', and don't know what value it should be. I can't find any similar problems in Google or this forum.

I tried removing the step and recreate it from scratch, with the same result. Posting an 'adaptive card' works, so the connection to Teams should be fine.

This is the code view of the step:

{
  "type": "OpenApiConnection",
  "inputs": {
    "parameters": {
      "poster": "Flow bot",
      "notificationType": "team",
      "body/recipient": "@items('Apply_to_each')",
      "body/previewText": "Nieuw proef-account: @{triggerBody()?['company']}",
      "body/channelRecipient/groupId": "e3a20e9b-d53e-4868-a55e-8e4023148b96",
      "body/channelRecipient/channelId": "19:41ae55653d68456997ab64f651738c70@thread.tacv2",
      "body/messageId": "@outputs('Adaptieve_kaart_posten_in_chat_of_kanaal')?['body/id']"
    },
    "host": {
      "apiId": "/providers/Microsoft.PowerApps/apis/shared_teams",
      "connection": "shared_teams_1",
      "operationId": "PostFeedNotification"
    }
  }
}

Categories:

Building flows

CleanShot 2024-10...

I have the same question (0)

All responses (34)

Answers (0)

scalca 243 Moderator on at

Like (1)

Report

what do you have in your apply to each ?

Was this reply helpful? Yes No
BS-08100930-0 2 on at

Like (1)

Report

Hello,
I have the same issue.

I did find any information about those changes.

My flow was working properly since 07/10

my input

{

"host": {

"connectionReferenceName": "shared_teams_1",

"operationId": "PostFeedNotification"

},

"parameters": {

"poster": "Flow bot",

"notificationType": "team",

"body/recipient": "eewfewkfhke-wdqdwdwed-wedqweq",

"body/previewText": "Notification Message Text",

"body/channelRecipient/groupId": "213l21k3l214-232324-1312-q21312",

"body/channelRecipient/channelId": "19:vHgo71buqYOBGtIV95FKduN5_10v023NY0O5k_t-W9M1@thread.tacv2",

"body/messageId": "AAMkAGE3OWM3NGEzLTc1YTctNGQwNC1iYjAwLTg5YmEwNmU4NGZlYgBGAAAAAAAynKYSWT3DTZvCZBy0BANaBwCmSv-DeP9uS5tShf712CQiAAAAAAEMAACmSv-DeP9uS5tShf712CQiAAFiA1EnAAA="

}

}

Was this reply helpful? Yes No
KG-08101252-0 2 on at

Like (1)

Report

Hello,

We are also facing the similar issue from yesterday onwards, no changes done on the flow which was working fine for last 4-5 months.

Also, in apply to each we have the email id of the people to whom the notification will go to teams feed.

Thanks in advance for helping on this.

Was this reply helpful? Yes No
scalca 243 Moderator on at

Like (1)

Report

did you try to refresh the connection ?
remove and add the action again ?

Was this reply helpful? Yes No
inserve 68 on at

Like (1)

Report

I created a new connection and assigned it to the flow step, but I get the same error. Recreating the step: also the same error.

The last successful notification was sent at 3 October 13:38 (Amsterdam time).

The for loop is just e-mail addresses of employees:

{

"name": "Users",

"type": "Array",

"value": [

"x@inserve.nl",

"y@inserve.nl",

"z@inserve.nl",

"a@inserve.nl",

"b@inserve.nl"

]

}

]

Was this reply helpful? Yes No
Jaimen 2 on at

Like (1)

Report

I too am having the exact same issue all of a sudden. My flow has been live since Feb 2024 without any issues and suddenly, since this morning, im getting this error consistently for each run.

Was this reply helpful? Yes No
Almeta 4 on at

Like (1)

Report

I am experiencing the same issue. Getting the error "The provided flow name '<null>' is not valid." with a flow that is supposed to work out of the box.

Was this reply helpful? Yes No
AA-10100744-0 3 on at

Like (1)

Report

Hello,

we face the same issue, anny solutions for this problem? We get a null value

Was this reply helpful? Yes No
DC-10100822-0 3 on at

Like (1)

Report

I too am getting the same issue.

Was this reply helpful? Yes No
SB-11101255-0 2 on at

Like (1)

Report

I have the same issue. Until a few days ago it was still working. Any solution?

Was this reply helpful? Yes No