I've had this issue as well. They were villagers I'd bred up before 1.14.4. One had a profession beforehand, the other was unemployed. Once 1.14.4 came out, I infected then cured both, and employed the second one as a librarian. I kept my librarians together in a 2x2x3 holding area, with three Lecterns as their workstations. I'd notice after I locked some trades they'd work and refresh. Sometimes it'd take longer than others, but usually within 30 seconds or so. Breaking eye contact and allowing them to work seemed to help, but I'm unsure. I've since moved them to another area for breeding, and will update once I get them into a trading hall if it still happens.
As far as I can tell the issue is likely cause by updating from an earlier version of 1.14, curing the villagers, or maybe giving them multiple workstations?
EDIT: I just read the report linked above, and it's a way better description of the problem. Should have read it before posting, but Alas, I did not. Thanks for the link, Johnibur!
Has this not been fixed yet I guess? I had this issue in one of my games, but I just tested it after update and it wasn't an issue. But I am afraid to sit my dogs if this is still a bug.
Justin Torres
I've had this issue as well. They were villagers I'd bred up before 1.14.4. One had a profession beforehand, the other was unemployed. Once 1.14.4 came out, I infected then cured both, and employed the second one as a librarian. I kept my librarians together in a 2x2x3 holding area, with three Lecterns as their workstations. I'd notice after I locked some trades they'd work and refresh. Sometimes it'd take longer than others, but usually within 30 seconds or so. Breaking eye contact and allowing them to work seemed to help, but I'm unsure. I've since moved them to another area for breeding, and will update once I get them into a trading hall if it still happens.
As far as I can tell the issue is likely cause by updating from an earlier version of 1.14, curing the villagers, or maybe giving them multiple workstations?
EDIT: I just read the report linked above, and it's a way better description of the problem. Should have read it before posting, but Alas, I did not. Thanks for the link, Johnibur!