Got the database - thanks!
About the bean... you're missing the identifiers (name) in the bean details. The "identifiers" are what Roastmaster considers to be the name of the bean. Since the country is also empty, the whole thing is showing up blank for you in the roast console.
For beans, you can break it down by Market, Grade, Estate and Variety if you want, or lump it all together into one of these. Roastmaster considers the sum total of these four strings to be the "name" of the bean. This combined string is what it displays in different areas of the app. Put "Greenline" into one of these in and you'll be set. The country will still be blank, but that is to be expected for a pre blended "bean". If you blended it yourself, or knew the components of the blend, you could optionally record it as a blend, then roast that blend instead of a bean.
Now, the time anomaly. I've done some testing myself today, and cannot duplicate it. The only thing that I can think of that would produce that is the iPad's clock changing time during a roast. Would your iPad's time have changed for any reason? Not that I think you'd carry your HotTop with you on a train
, but if you went eastward on a train into the next time zone, and the iPad's time went back 1 hour during a roast, I could see something like this happening.
Otherwise, I'm at a loss. I can tell you that no one's reported this before, and I've never seen this happen for me, so hopefully we can chalk it up to the iPad becoming temporarily confused about what time it was. If you think of any other time-related even that would have occurred during the time of the roast, let me know. I hate not knowing the cause of issues when folks encounter them - I'd much rather know exactly why something happened, so I can make sure it's not a bug in Roastmaster's code and know a definitive answer. But, sometimes that not possible.
Definitely let me know if you ever see this happen again. Make sure to note anything else you were doing on the iPad during the roast. Beyond a minor graphical bug or two, there aren't any significant bugs that I'm aware of at the moment, and I'd squash it quick if it proved to be a Roastmaster bug.
Danny