jasquat

We could queue the instance again if the lock error occurs. It shouldn't cause an issue only maybe slightly less efficient.

I did a force run on 39311 and it did continue on so it can run. I'm still not sure why this happens though. We may need to create a...

For 35865, the task with a timer is ef6db7d5-4a7b-4897-aeac-b96233927c2d and that is in the future_task table: ``` [spiff-workflow-backend]> select guid, from_unixtime(run_at_in_seconds) from future_task where guid = 'ef6db7d5-4a7b-4897-aeac-b96233927c2d'; +--------------------------------------+----------------------------------+ | guid...

@madhurrya we updated dev.mod with timer fixes. It should be ready to test.

Yeah that makes sense. Start events are still processed by the "not_started" background processor. It would be nice to move that over to celery AFTER the initial celery release. It'll...

@madhurrya what's the original issue? timer start events specifically? This ticket has just blown up since then so we need to get a handle on what this ticket is actually...

This seems to be related to the comment here https://github.com/sartography/spiff-arena/issues/1861#issuecomment-2206467374.

@madhurrya I'm not sure. My comment was based on what @essweine was saying in slack. This issue could be unrelated and could actually be caused by too many tasks over...

I tried to get the serialized json but the process I was running - `poetry run python bin/get_bpmn_json_for_process_instance.py 35667` - was killed. I'm not sure we can export the instance...

``` {% set note_index = 0 %} {% for item in ['hey', 'yo'] %} {% set note_index = note_index + 1 %} {{ item }}: {{ note_index }}: {{ loop.index0...