Newly configured Custom bot is not responding when customer is testing using "Hi or Hello" keywords.Issue When the customer tried to test the bot by sending a "Hi" command from the Teams bot, the bot did not respond back and we observed outbound was not delivered in the sys_cs_conversation table.ReleaseNACauseCustomer has recently cloned the instance and Script includes with protected policy are encrypted on install (outside of zboot/upgrade by non-maint users) and decrypted before execution. If a script include has a protection policy as protected, then the data in the script is encrypted on the instance when the script gets installed (e.g. from the ServiceNow Store, or a plugin). The protected script is encrypted with Triple Data Encryption Standard (3DES). Starting from Washington release, the protected script is encrypted with Advanced Encryption Standard (AES) algorithm by default. In some clone scenarios, the protected script include decryptions are failing.ResolutionDuring our investigation, we reproduced the issue and verified the associated flow executions. We observed that the flow is failing with the following error: WARNING *** WARNING *** Evaluator: com.glide.script.RhinoEcmaError: illegal character sys_script_include.******************.script : Line(1) column(1) This indicates a problem related to a Script Include, likely due to encryption. To proceed with verification: > Navigate to Script Includes. > Add the fields Protection Policy, Script and Application to the list view. Set the Application to Conversational Interface with Microsoft Teams. Upon inspection, we confirmed that the script is encrypted. This encryption appears to be the root cause of the flow failure. As part of our troubleshooting, we repaired the following plugins: Azure Active Directory User Mapping Conversational Integration with Microsoft Teams After completing the plugin repair, refresh the Script Include table. The previously encrypted script should now be decrypted and viewable. At this point, please retry reproducing the issue. It should now function as expected.