Author Topic: Cloud issue  (Read 2898 times)

Offline yegnal

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 10
  • BeerSmith 2 Rocks!
Cloud issue
« on: August 22, 2018, 11:06:54 AM »
**** Error ****

When I try and open a cloud recipe, I get "recipe is currently open for editing on another computer - please try again later"

This occurred after beersmith crashed while editing this cloud recipe, question is how do I regain access to it.   It's a WeeHeavy currently in primary right now, soon to be moved to secondary and adding some oak cubes.....

Offline BeerSmith

  • Brewer, Author, Patriot
  • BeerSmith Administrator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 5419
  • BeerSmith - take the guesswork out of brewing!
    • BeerSmith
Re: Cloud issue
« Reply #1 on: September 06, 2018, 07:12:12 PM »
The lock on the recipe will actually time out by itself in about an hour.  After that you can edit it again.

Get a free trial of BeerSmith 3 here

Offline piwo

  • BeerSmith New Brewer
  • *
  • Posts: 1
  • BeerSmith 2 Rocks!
Re: Cloud issue
« Reply #2 on: September 29, 2018, 07:13:49 AM »
My brew area is just on the edge of my wifi coverage which is where I mostly use Beersmith.  I often try to print from that area and if it wifi is spotty Beersmith will lock up.  This of course should be expected.  My problem is that once this happens, i have to terminate Beersmith.  Once i terminate Beersmith, I cannot open the file for an hour.  This is very inconvenient on a brew day.  Is there no way to delete a lock file or something other that delay everything for an hour?

Offline slipring

  • BeerSmith New Brewer
  • *
  • Posts: 1
  • BeerSmith 2 Rocks!
Re: Cloud issue
« Reply #3 on: October 05, 2020, 07:26:23 PM »
I copied the recipe to local and was able to open it

Offline Brew Bama

  • BeerSmith Master Brewer
  • ****
  • Posts: 57
Re: Cloud issue
« Reply #4 on: Today at 07:47:57 PM »
I print the brew steps just before brewday to capture any audibles just in case there?s a glitch with BeerSmith on brewday. I?ve yet to encounter a glitch but better safe than sorry.