Keith Stevenson

@MacLean Ferguson Also https://status.hornbill.com/ is the URL to access . That was not effected Kind Regards

@MacLean Ferguson This is now restored. We will be providing a full report later once we finish tidying the remaining issues up Kind Regards

@MacLean Ferguson Since around 20:10 the cluster of machines hosting your instance has suffered a disk issue. We are looking to resolve. KInd Regards

@Martyn Houghton We can inform you that this has been added in the new UI , there is now an option next to compose to rename any non system folder. Kind Regards Hornbill Cloud Team

All, The ESP release containing the fix went live this morning and testing shows the issue with Keysafe creation no longer occurs. Kind Regards Hornbill Cloud Team

All Thanks for the information. We have now replicated and resolved the issue inhouse. This will be part of tomorrows 5AM ESP update . Kind Regards Hornbill Cloud Team

All, Thanks for the posts. We are checking the change. Kind Regards Hornbill Cloud Team

@Berto2002 Just to clarify the change made is to specifically fix the ""Instance endpoint call failed" on the creating KeySafe. Not any other issue and it should be this that is tested\confirmed. Kind Regards Hornbill Cloud Team @Adith Will make the change to your instance now.. Give it 10 minutes and test again Kind Regards Hornbill Cloud Team

@JamesGreen We have identified an issue with the generation of new Key Safe items and made a change that should resolve this. Can you try again and confirm Kind Regards Hornbill Cloud Team

@Mike Hillman Thanks for the post. We have had 1 other customer report something similar when trying to set Sub Statuses . We are investigating. Kind Regards Hornbill Cloud Team

@Mike Hillman Thanks for the post. We cant see anything unexpected in the logs and everything appears normal. Can you confirm if the comment appears after a refresh of the browser? If that still doesnt post as expected can you create a HIR file and send this via direct message. Kind Regards Hornbill Cloud Team Generate a HAR file in Chrome Close all incognito tabs and windows in Chrome. Open a new incognito window. Click the more actions menu (...) to the right of the toolbar and select More toolsDeveloper Tools. Select the Network tab. Ensure that Chrome is recording. A red button indicates that a recording is already in progress. Otherwise, click Record network log. Select Preserve Log. Clear any existing logs by clicking Clear network log (). Go to the page where the issue occurred and reproduce the issue. Click Export HAR (the down arrow icon) to export the file as HAR. Save the HAR file. Generate a HAR file in Firefox Close all private tabs and windows in Firefox. Open a new private window. Go to the page to be recorded. Click the application menu () and then More toolsWeb Developer Tools. In the developer tools docked tab select Network. Go to the page where the issue occurred and reproduce the issue. The page automatically starts recording as you navigate. When you're finished, click Pause/Resume recording network log. Right-click anywhere in the File column and select Save All as HAR. Save the HAR file. Generate a HAR file in Safari If the Develop menu doesn't appear in the menu bar, go to SafariSettings. Click Advanced. Select Show Develop menu in menu bar. Close all private tabs and windows in Safari. Open a new private window. From the Develop menu select Show Web Inspector. Click the Network tab. Go to the page where the issue occurred and reproduce the issue. When you're finished, click Export. Save the file. Generate a HAR file in Edge Open Edge. Close all InPrivate windows. Press Ctrl + Shift + N to open a new InPrivate window. Click the Settings and more menu (...) to the right of the toolbar and select More toolsDeveloper tools. Click Network. Ensure that Edge is recording. A red button indicates that a recording is already in progress. Otherwise, click Record network log. Visit the page and complete the steps that trigger the issue. When you're finished, click Stop recording network log. Click Export HAR (the down arrow icon) or press Ctrl + S to export the file as HAR. Save the HAR file.

@Mark Priest Thanks for the post. This is most likely something on the users network or machine blocking access to our URLs. We see this from time to time with BT users who have Parental controls enabled and the following post may help with those )

@LawesD This does appear to be a problem with your SMTP server for port.ac.uk in the way its terminating TLS connections. The first error was at 2023-11-03 10:22:02Z [INFO]:[GENERAL]:[1084] MAIL: Failed to send message data: ChilkatLog: You will need to contact the admin of the SMTP server and ask them to investigate. Kind Regards Hornbill Cloud Team

@Malcolm The check for which user to log the call against will look at the h_email field in the h_sys_accounts table (users).. In your instance the test email address (from ) you used (which was your own) is set against your own user and the admin account. These can be configured in the Platform Admin -> User section Kind Regards Hornbill Cloud Team

@Malcolm Thanks for the post. From the logs it appears that it fails to log the call as more than 1 account has the same email address and therefore it cant decide which 1 to use. You should update the accounts with duplicate email to remove the ambugity 2023-10-24 08:01:49Z [INFO]:[SYSTEM]:[8012] Processing auto-e-mail-responder request ... Subject: Re: Test Automation Boom 2023-10-24 08:01:49Z [WARNING]:[COMMS]:[8012] Operation[apps/com.hornbill.servicemanager/arOperation::raiseNewRequest] /apps/com.hornbill.servicemanager/flowcode/fc_ar/raiseNewRequest.js(305): error X1001: Uncaught Found more than 1 account with the same email address. Kind Regards Hornbill Cloud Team

Chris Thanks for the post. We can see no issues with connectivity and our monitoring of all instances from 5 remote locations showed no issues. During the time post we can also see users accessing your instance. Kind Regards Hornbill Cloud Team

Dear Customer Unfortunately, BTs (And therefore any subsidiary such as PlusNet etc) parental filters are blocking valid Hornbill URLS due to an incorrect listing on their system. As this is a BT issue and not a Hornbill issue and as Hornbill are not BT customers we are unable to escalate to them or resolve. We therefore recommend that you send via the BT support channels that you as a customer of BT has the below. The problem will manifest as shown in the below image when using a BT (or Subsidiary service) with Parental Filters enabled. ======== Dear BT The below URL is being incorrectly intercepted by your parental control filter mdh-p01-api.hornbill.com This is being DNS poisoned and returning IP of 81.130.111.239 i(or similar) instead of the expected 78.129.173.117 The Address mdh-p01-api.hornbill.com/78.129.173.117 is owned by Hornbill Technologies and should not be blocked. Please unblock this ASAP ======== Kind Regards Hornbill cloud Team

@Jim No at the moment its all Kind Regards

@Nikolaj Thanks . I can now replicate the issue. Will investigate. Kind Regards

@Nikolaj Thanks for the post. We can see no errors in the logs. If the file is not sensitive can you send it me in a PM or just the file name. Kind Regards

All, There was a cloudflare DNS issue this morning for a 2 hour window. You may have seen intermittent mail delivery failures, however the emails should have been resent automatically Here is a link to the cloudflare status page. https://www.cloudflarestatus.com/#past-incidents Kind Regards Hornbill Cloud Team

Stuart, Thanks for the post. Yes. In Admin under Platform Configuration-> Customize then Login Screen Kind Regards

The latest update from MS.. They have rolled out a fix and should be completed at 5PM UTC Title: Some users may be unable to access their mailbox using the IMAP4 connection method within Exchange Online User impact: Users may be unable to access their mailbox using the IMAP4 connection method within Exchange Online. More info: All other connection methods are unaffected by this issue. Current status: The fix has been approximately 97% saturated to affected users, and we estimate completion by our next scheduled update. Scope of impact: Impact is specific to users hosted through the affected infrastructure and may impact any user attempting to access their mailbox using the Internet Message Access Protocol (IMAP4) connection method within Exchange Online. Root cause: A configuration issue within a recent change to enhance the user experience to the IMAP4 connection method, is inadvertently causing impact. Next update time: Friday, August 11, 2023 at 5:00 PM GMT+1 Kind Regards Hornbill Cloud Team

All, MS Are reprting issues with IMAP connections. See System Health in your MS Portal. This is not a Hornbill Issue Some users may be unable to access their mailbox using the IMAP4 connection method within Exchange Online EX666988, Last updated: August 11, 2023 at 10:26 AM GMT+1 Estimated start time: August 11, 2023 at 8:53 AM GMT+1 Kind Regards Hornbill Cloud Team

@billster Thanks for the post. If you try again this should no longer occur. It seems that during this monrings update the index didnt reopen. We have manually done this and performed a reindex to ensure all data is correct. Kind Regards Hornbill Cloud Team