ali
/
invoice_az
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(amas): clarify why import stays on the default queue 

The "short" queue caused the import to run concurrently with the
post-setup desk load and deadlock on the tabSessions row. Document that
default is intentional; the queue arg stays for callers that need it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ali 2026-06-15 16:36:04 +00:00
parent a275f4144e
commit 9aab62d5e4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
invoice_az/amas_api.py
View File

@ -2736,10 +2736,10 @@ def import_bulk_employees(asan_login_name, employees_data, company, create_desig
Refuses to enqueue if an import for the same Asan Login is already running.
``queue`` lets callers pick a less-contended RQ queue. The setup wizard passes
"short" so the import isn't stuck behind the pile of post-setup jobs on the
default queue (a single `bench worker` drains queues short→default→long, so
"short" jumps the line and starts as soon as the worker frees).
``queue`` lets callers pick the RQ queue. Default "default" is deliberate:
routing to the higher-priority "short" queue makes the import run immediately
and concurrently with the post-setup desk load, and the two deadlock on the
tabSessions row (CSRF token write). Prefer a slightly later start over that.
"""
if isinstance(employees_data, str):
employees_data = json.loads(employees_data)