Sahana. Shenoy Posted February 4 Posted February 4 Hi All, We are getting below error suddenly upon using the Team's chat functionality which was working fine until yesterday. We have not made any changes and its giving error while using any Team's chat button. Thanks/Sahana Xmlmc method invocation failed for BPM invocation node 's1/flowcode-b90f844f': 0207 apps addNotice /apps/com.hornbill.core/flowcode/fc_modules/xmlmc.js(189): error X1001: Uncaught EspMethodCall::invoke: Operation[data::entityAddRecord] The text size provided (258 characters) is greater than the maximum allowable size of 255 characters for column h_sm_request_notices:h_text Execute /apps/com.hornbill.core/flowcode/fc_modules/xmlmc.js 189 20 Uncaught EspMethodCall::invoke: Operation[data::entityAddRecord] The text size provided (258 characters) is greater than the maximum allowable size of 255 characters for column h_sm_request_notices:h_text 1001 invoke at /apps/com.hornbill.core/flowcode/fc_modules/xmlmc.js(189:21) entityAddRecord at /apps/com.hornbill.core/flowcode/fc_modules/xmlmc.js(547:54) entityCreate at /apps/com.hornbill.servicemanager/entities/RequestNotices/fc_modules/request_notices_helper.js(142:25) run at /apps/com.hornbill.servicemanager/entities/RequestNotices/fc_bpm/addNotice.js(51:39) at /apps/com.hornbill.servicemanager/entities/RequestNotices/fc_bpm/addNotice.js(14:1) Close
Steve Giller Posted February 4 Posted February 4 The issue is as reported by the error: The text size provided (258 characters) is greater than the maximum allowable size of 255 characters for column h_sm_request_notices This is nothing to do with the Teams chat, it is caused by trying to add a Request Notice where the notice text is longer than the allowed 255 characters. I don't know where the message text is coming from - but if it's from a user input please ensure that this input has a maximum length restriction of 255 characters to prevent this issue.
Sahana. Shenoy Posted February 4 Author Posted February 4 @Steve GillerThe text size provided (258 characters) is greater than the maximum allowable size of 255 characters for column h_sm_request_notices:h_text Execute. How come this error started as of a sudden which was working fine until yesterday. As we use this button very often. Never faced this issue earlier and no changes made to this functionality from our end.
Sahana. Shenoy Posted February 4 Author Posted February 4 Below is the screenshot, where the h_text doesn't cross that character limit.
Steve Giller Posted February 4 Posted February 4 As mentioned above, the error is: The text size provided (258 characters) is greater than the maximum allowable size of 255 characters for column h_sm_request_notices I'm not sure why you're looking at anything else. 5 minutes ago, Sahana. Shenoy said: How come this error started as of a sudden which was working fine until yesterday. Because you've never presented a message of over 255 characters before today. 5 minutes ago, Sahana. Shenoy said: As we use this button very often. Never faced this issue earlier and no changes made to this functionality from our end. This is nothing to do with functionality, it is simply because you've never presented a message of over 255 characters before today. If you can imagine you have a cupboard, and every day you replace the contents with 255 boxes of pens and shut the door. Then one day you put in 258 255 boxes of pens and find the door will not shut. There is nothing wrong with the cupboard, it's just that today you've put too many boxes in. It holds 255 boxes, it does not hold 258. 16 minutes ago, Sahana. Shenoy said: We have not made any changes Yes, you have, you have changed the length of the message and it is too large.
Steve Giller Posted February 4 Posted February 4 The screenshot above does not show any messages that are too long because that one was never entered into the database because it was too long. As it could not make a database entry it generated an error - the one in your initial post.
Victor Posted February 4 Posted February 4 @Sahana. Shenoy I’m not sure how much more help we can offer, as this doesn’t seem to be a problem with the system or your Teams settings. The issue is that the notice you’re trying to create in Hornbill is too long - it’s 258 characters, but the limit is 255. As Steve mentioned, you might not have run into this before, but as long as your text for notices don’t go over the character limit, you shouldn’t have this problem again.
Sahana. Shenoy Posted February 4 Author Posted February 4 Hi @Steve Giller & @Victor, thanks for the response. But how could I identify where the character limits have exceeded? Is it in the Auto Task or workflows which I need to check.
Victor Posted February 4 Posted February 4 @Sahana. Shenoy we currently lack sufficient information to provide a definitive answer. The error message you posted has been explained, but without details about your configuration and setup, we cannot ascertain the specific root cause and where it originates from. It appears you have a component (potentially an integration or another element) utilised within Teams chat (or it appears as such), which is generating a notice on a request. This component uses certain text (possibly sourced from Teams chat or another origin) to create the notice, and this particular text is causing the issue because this text is too long - it’s 258 characters, but the limit is 255.
Steve Giller Posted February 4 Posted February 4 @Sahana. Shenoy That is impossible to say - we don't have access to your Instance, and as this is a configuration issue this should not be something to diagnose internally. I can say that Something is trying to create a Request Notice almost certainly a node in either a Workflow or an Auto Task It is likely that the text for the Notice is a variable This may be text entered manually, or generated from other data, e.g. {{Username}} has reported {{issue}} with {{system}} On this specific occasion the message has exceeded 255 characters. Where the message comes from and how it got to be too long is not something we can diagnose on the forum, however you can engage Expert Services if you require Hornbill to reconfigure your Workflow/Auto Task for you.
Jules2218 Posted Wednesday at 15:30 Posted Wednesday at 15:30 For anyone that is having this issue. We raised a customer support ticket and the issues was caused: "The issue involved existing MS Teams keytype app registrations failing when creating new keys, while refresh tokens were unaffected. This was due to Microsoft deprecating an old authentication endpoint. From the error provided, we identified this and adapted to the Microsoft changes. All tests are completed, and the system is now functioning correctly. By outputting the workflow (MS team) failure error message to the Timeline of the Request, future investigations will be facilitated in case of failures. As previously mentioned, there is no restriction on the amount of text allowed in this field." 1
Steve Giller Posted Wednesday at 15:50 Posted Wednesday at 15:50 Just to clarify for anyone reading this, the error message reported on the initial post was purely that the length of the message was too long to fit into the Request Notice. In case anyone else sees that error it's important to know that this was not related to the Teams issue, it was just that the message could not be seen initially.
Victor Posted Wednesday at 16:22 Posted Wednesday at 16:22 @Jules2218 @Sahana. Shenoy while you were indeed affected by the issue caused by Microsoft deprecating an old authentication endpoint, that is not the issue raised and being discussed in this thread. Based on the copy of the error message presented, this thread specifically reports a problem encountered when creating Hornbill request notices. So, to provide further context and full clarity, to anyone reading this thread, since there are some actions that happened outside this thread, here is a breakdown of the key elements: The Microsoft Deprecation Issue (Resolved) Microsoft deprecated an old authentication endpoint, which caused the Teams Chat integration to fail. This failure generated an error message containing 258 characters. The Hornbill Request Notice Issue (The Subject of This Thread) The request notice was designed to use the error message from the Teams Chat integration failure as its text. However, Hornbill request notices have a strict character limit of 255. Since the error message exceeded this limit, the request notice failed to be created, leading to the issue reported in this thread. In summary, while the Microsoft deprecation issue was the trigger for the Teams Chat integration failure, the actual issue being discussed here is the unintended consequence of using an error message that exceeds Hornbill’s character limit for request notices.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now