For anyone reading this, I contacted support, and they recommended I disconnect the local company from Sage ID then reconnect, which I've done - hopefully this has worked, but will see over the coming days: gb-kb.sage.com/.../viewsolution.jsp

Thanks for the update, Jon. Will try as well.  Fingers crossed.

Another update: one user let me know that they had to sign into Sage Drive again this morning, despite me disconnecting/reconnecting the company from Sage ID last week, then re-adding the company for them.

This user was in the office last week - this week they're at home. I wonder if it has anything to do with Sage detecting the IP address used to connect?

Hi Jon,

We're currently investigating this issue. At this stage I'm unable to confirm where the issue is (program or service side) but we have logs of the problem and busy looking for the route cause.

Once that investigating is complete I'll come back with the answer. For the time being it will be a case of logging in when prompted.

Ian

Great, thanks Ian.

Hi Jon, I have the same problem, since upgrading to V27. Have you managed to find a fix? I am still waiting on Sage to get back to me and it's just getting a little tiresome. Also, again since the upgrade, Sage just closes without warning from time to time.

Hi Both,

I can confirm that this has now been fixed and will be deployed as part of v27.1 which is due in late December.

Hope this information helps.

Ian

Hi Ian, thanks for getting back to me so quickly.

You say this has now been fixed but we will have to wait another month before we can have the fix? Or am I misunderstanding? It is quite irritating to have to keep signing in each day, to each client and take up valuable time also. 

The sooner this is fixed the better please.

You really would think that for a fix that is this disruptive to their customers, they would pull out all the stops & move it LIVE as soon as possible & not wait for another release date!! Just call it v27.0.1.....Again, not customer service we would expect.

Hi Both,

I can appreciate it's frustrating having to keep signing in each time and having to wait for a fix is never ideal.

This issue was reported to us during November and required product delivery to investigate the issue to find out what was going wrong. Unfortunately, the issue can not be fixed service side requires an update to the program to handle the exception. It's worth saying that this issue only impacts users using Sage ID with certain serial numbers. As v27.1 is complete and going through testing it was decided to include this fix as part of that rather than a separate update due to the amount of testing it'll go through (around 400+ hours)

We're looking to be finished on the 17th of December and then customer services will look to release the update.

Hope this information helps,

Ian