Hello! I have some funky logic that I want to make sure I am configuring correctly. I have a fetch a lock that happens on the sales order header where writeSalesOrders is called if new lines have been inserted to the record. I follow that call with a call to a background logic that will also access…

haha yes Ian started that thread because of me lol. This one is a little more specific, so just making sure with the nested/background call I am not doing something wrong.

This doesn’t sound like a candidate for a deadlock. However, if everything is routed through the Sales Order header, lock timeout is definitely possible. There are always 2+ records involved in a deadlock. Deadlock basics: process X1 has a lock on record A and needs to lock record B process Y1 …

@ian.p is right. You will not have a deadlock but you are definitely at risk for a lock timeout. The originating process and the background task are both trying to get a lock on the same record. If the background task is picked up before the original process ends, its Fetch And Lock action will have…

Thank you all for your feedback! It does appear I am running into a lock timeout so I will try your proposed solution Brendan.

What is the difference in functionality of calling a background LB directly with the call LB action vs using this queue back LB action? Was the best practice here?

Great question, maybe worthy of its own post. Queue a Background Logic Block will always queue up the specified logic block to run in a separate background process. It provides the additional “Queue Immediately” checkbox that you need to specify behavior specific to queueing. For Call A Logic Bloc…

So my use case is kicking off from an insert to a table that happens during a workflow event. Just so I know I am understanding correctly, this falls into asynchronous functionality, correct?

It depends on whether the workflow event is synchronous or not. If it’s part of a Manual or Logic Block transition (from a synchronous logic block), then it’s synchronous. If it’s an automatic transaction, it’ll be asynchronous.

Nested fetch and locks

Nextworld Platform

Aaron.C July 17, 2025, 12:14am 2

Possibly a related thread but perhaps does not answer your exact question

Topic		Replies	Views
Queue Background Task vs Call Logic Block on the Background-Task Logic Block Nextworld Platform	3	71	September 12, 2025
Background logic block can't access details from calling logic block Nextworld Platform	5	67	July 16, 2026
Expected Fetch vs Fetch and Lock behavior for parallel processes Nextworld Platform	3	82	July 9, 2025
Error_executing_query_lock_timeout Nextworld Platform	5	70	October 13, 2025
Queue background tasks with the same sequential key Nextworld Platform logic-blocks	2	54	July 17, 2025

Nested fetch and locks

Related topics