Chat ID returns unknown error

Question

After querying the user's chats, we found 2 chats with different ID's. One with the usual id: 19:user-1-id_user-2-id:@unq.gbl.spaces. The other with an ID we've not seen before: 48:notes

After further looking further into this, we found the content to be similar
{"chatId": "19:user-1-id_user-2-id:@unq.gbl.spaces", "body": {"contentType": "html", "content": "<p><span style=\"font-size:14px; font-style:inherit; font-weight:inherit\">... this morning and afternoon</span></p>"}}

{"chatId": "48:notes""body": {"contentType": "html","content": "<p>... this morning</p>"}}

Note that there is added text to the correct chat, as well as the added <span/> tag

When querying /v1/chats/48:notes, we get the error: {"error":{"code":"BadRequest","message":"{\"errorCode\":0,\"message\":\"Notes is not flighted\"}, ...}". We're not totally sure what the error means, but it seems like this feature is not yet turned on yet?

Can't seem to find any documentation on this error either.

Other Notes:

1. This conversation is a 1v1 conversation, when querying the other user of the conversation, we find the message with the right chatId, but not with 48:spaces chat.
2. When calling /v1/notes/:user_id, we get response: {"error": {"code": "BadRequest", "message": "Resource not found for the segment 'notes'.", ...}. So I'm not sure that notes have been set up for this user.
3. When calling /v1/chats/51:notes or /v1/chats/25:notes, we get the response: {"error": {"code": "BadRequest","message": "{\"errorCode\":201,\"message\":\"The Thread Id is invalid\"}"....},. Leading us to believe that 48:notes is a valid chat id.

Answer 1

Hi, we are getting the same error as well:

we are calling this API ==> https://graph.microsoft.com/v1.0/chats/48:notes?%24expand=members

and it gives below error:

"error":{"code":"BadRequest","message":"{\"errorCode\":0,\"message\":\"Notes is not flighted\"}"

we couldn't find any information anywhere about above error!

Thank you.

Answer 2

Has there been any update to this? We are still seeing the error. We are also seeing a new different error that we can not find any documentation on, andare wondering if there is any relation to the original error.

{"code":"BadRequest","message":"allowDeletedChannels is not allowed for non-private channels","innerError":{"message":"allowDeletedChannels is not allowed for non-private channels","code":"InvalidRequest","innerError":{},"date":"2022-09-06T23:24:20","request-id":"6b91c7dc-45fb-41f5-bae4-9552625c1e0e","client-request-id":"6b91c7dc-45fb-41f5-bae4-9552625c1e0e"}}}

Answer 3

Hi folks, so just any FYI for those who dont know yet.

48:notes is the threadId for self chat aka, messgaing with your self, refer to the image.

Apparently this has been rolled out completely, you should be able to see the self chat. Regarding the error pinged the internal team to see what's going there because you folks should be able to pull info for 48:notes.

Also just FYI. 48:notes for your user would not be created in our db until you folks actually send a message to yourself just like any other chat.

Answer 4

Hi,

Even if the feature seems to have been rolled out on our tenant, and I already sent a message to myself in the Teams client, I cannot get information from my "48:notes" chat from the Graph API.

I am trying to setup a Logic App (or a Flow) to send myself a daily reminder of my ongoing tasks.

Thank you !