1C Workflow - routine tasks are not performed, an error occurs, what could be the reason?

Question

1C

Platform Version: 1C:Enterprise 8.3 (8.3.10.2299); version 1C: workflow: Workflow 8 CORP, edition 2.1 (2.1.12.2).
Business processes are stuck. A job execution error appears in the log. Has anyone come across? Error code:

{ОбщийМодуль.РаботаСЭП.Модуль(1031)}: Ошибка при вызове метода контекста (ЗаблокироватьДанныеДляРедактирования)
        ЗаблокироватьДанныеДляРедактирования(ПодписанныйОбъект,, ИдентификаторФормы);
по причине:
Ошибка блокировки объекта. Объект уже заблокирован:


{РегистрСведений.ЗадачиДляВыполнения.МодульМенеджера(212)}: Ошибка при вызове метода контекста (Заблокировать)
по причине:

по причине:
В данной транзакции уже происходили ошибки!

Answer 1

Yes, I remember such a piece of code - in DOs they like to do a check before manipulations using LockDataForEditing(). And I also remember that there are a lot of background ones hanging there, including an endless recalculation of rights. And yet, users could work from a browser or a mobile client and their session hung ... In short, you need to restart the server.
If there is such an opportunity, then I recommend at least once a week to routinely overload the 1C service on the weekend.
PS Or you can set up extended logging of the technological log and, at the next blocking error, track who blocked it there before - a person or a scheduled task. Further decision on the circumstances.
UPD. If you are connected to the interaction system, you can remove the lock yourself without having to reboot the server. From the task that you cannot complete, go to the subject (as I understand it, we are talking about an internal document) and try to edit it. You will be prompted to remove the lock. Read more here:
https://wonderland.v8.1c.ru/blog/vzaimodeystvie-pr...

Answer 2

This occurs if there is a session in which this object is locked for editing. Either programmatically (for example, a parallel background task), or interactively - the 1ski client is opened and this object is opened in it and its modification is started. The easiest way is to first cut down all sessions, and then check again. In general, the text of the error should write what kind of user the session that set the lock is, and so you can find where it came from.