We have released the hotfix to correct the sorting error. We also decided to align sorting in all tabs with the same priority as we had in present/approve tab. Priority is as follows:
​
Priority 1: Shift status (if shift/period status different than new)
Priority 2: Matching percentage
​
On equal number of shift statuses between two candidates (ex two candidates accepted 2 shifts of 5 total), they are also sorted by priority 2; matching percentage.

We are testing the fix and will release it as a hotfix as soon as possible

After a recent technical upgrade, we are currently experiencing issues with sorting candidates based on shift status in "Approve/Present to customer" and "Register" tabs. We are working on resolving the problem ASAP.

All links seem to finally have been migrated to the new domain. Get in touch if you still have trouble with links in Globus.

We are patiently waiting and have reached out again to our contacts in Recman.

We are still waiting for information from Recman on when the links issue is resolved for all environments. We will continue to update this page.

Recman has acknowledged the issue with the links, and they have informed us that they will release a fix shortly. We will update the page when the problem is resolved.

We were recently notified that candidate and customer links from Globus to Recman were not working. We contacted Recman, who informed us that they had changed their URL from "app.recman.no" to "app.recman.io" for certain links. We made an update yesterday to resolve the issue and update all links in Globus to the new domain. But today we found that the links in Recman are not consistent across all Recman environments. Some still have the old domain ".no" while some have the new ".io". This is causing issues for users on the old domain. We are in contact with Recman to try to figure out why the links are not consistent for all. We will update this page when we have further updates.

The missing role issue is resolved. The fix is working and full ETL run is completed for all tenants. Recman have confirmed that this was a bug in their API after a release they did on 6. July.

UPDATE: The fix has just passed code review and has been merged to Production. We will run full ETL for all the tenants. It should be fully completed within approximately 1h 45mins.

UPDATE: Preliminary exploration suggest that this error is due to RecMan unexpectedly changing their API contract. We will keep investigating and fixing the issue.

We are experiencing a problem where candidates are missing roles on some tenants. We are working on correcting this error with highest priority.

The connection issues have been resolved. We are still closely monitoring the application. As part of the fix we found it was most likely related to some undetected change in Chromium, which is the foundation for both Chrome and Edge browsers. For now, we have resolved the issue with a temporary workaround as we found the problem was related to request cancellation, meaning when you click something in the application it requests the related data, if you click something else before the application finishes loading the data from the first click, we cancel the request. These cancellations caused connection errors in the browser. We could not replicate these issues outside of the browser so it seems it is at the network layer of the browser.
​
We will continue to work on this to ensure request cancellations are managed correctly and not cause further problems.

It seems like fixes released during the weekend did reduce the occurrence of the connection errors. User reports and logs show improved performance and reduced connection loss issues. Yesterday we released another fix at 13.30 CET related to request cancellations that seem to have resolved most of the connection issues. We will continue to monitor the performance and please get in contact with us if you are experiencing issues.

During the weekend we released several fixes to mitigate the connection issues in Globus. Unfortunately, these fixes did not resolve the connection issues. The biggest challenge has been consistently reproducing the error to find the root cause of the problems, as we see that the issues stem from the browser/network layer. We are working with the entire product team and are now working with two main hypotheses to resolve this. We will release multiple updates during the day.
​
We again apologize for the inconvenience and are very sorry for those affected by the interruption in our services!