[{"data":1,"prerenderedAt":132},["ShallowReactive",2],{"blog-en-background-jobs-queues-1tool":3},{"id":4,"title":5,"body":6,"categories":112,"date":114,"description":12,"draft":115,"excerpt":116,"extension":117,"image":118,"lang":119,"meta":120,"modified":121,"navigation":122,"noindex":115,"path":123,"related":116,"seo":124,"seoDescription":125,"seoTitle":126,"slug":127,"sourcePath":128,"sourceRoute":116,"stem":129,"tags":116,"translated":115,"type":130,"wpId":116,"__hash__":131},"blog\u002Fen\u002Fblog\u002Fbackground-jobs-queues-1tool.md","How 1Tool works in the background: jobs, queues and scheduled tasks",{"type":7,"value":8,"toc":102},"minimark",[9,13,18,21,25,28,32,35,39,64,68,79,85,88],[10,11,12],"p",{},"Not every action in business software has to be finished the moment it is triggered. An import, a report or a sync with an external system can easily take a few seconds or minutes — as long as the user interface stays responsive in the meantime. 1Tool implements exactly this separation consistently: many processes do not run synchronously while a user waits, but are placed in a queue and worked through in the background. This is complemented by fixed, recurring scheduled processes that run independently of any specific user action.",[14,15,17],"h2",{"id":16},"queues-instead-of-waiting-why-background-processing-keeps-the-interface-fast","Queues instead of waiting: why background processing keeps the interface fast",[10,19,20],{},"If an action had to be fully processed the moment it was requested, every longer operation would block the user interface — the user would see a loading indicator until the very last step was complete. 1Tool avoids this by placing more demanding processes in a queue. The request itself is acknowledged immediately, and the actual processing then continues in the background. The result: the interface stays fast and responsive at all times, even while a more compute-intensive task is running in the background.",[14,22,24],{"id":23},"scheduled-processes-what-runs-automatically-and-when","Scheduled processes: what runs automatically and when",[10,26,27],{},"Alongside the event-driven queue, 1Tool runs a series of recurring, automatically scheduled tasks. Several parser processes — for tickets, costs, emails, projects and leads, among others — run every five minutes and make sure that incoming information from various sources is captured in a structured way without delay. A sync with connected bank accounts via finAPI runs several times a day. And a dedicated process checks every single minute whether a time-based automation is due and needs to be executed. In addition, 1Tool automatically cleans up old automation logs and expired access tokens every day, so the system doesn't get cluttered with outdated data.",[14,29,31],{"id":30},"what-this-means-in-everyday-work","What this means in everyday work",[10,33,34],{},"This architecture has a concrete, noticeable effect: a bank transaction that has just been imported does not necessarily appear in 1Tool in the same second, but is processed during the next scheduled finAPI sync. This is not a bug but a deliberate choice in favour of stability — rather than processing every single bank transaction individually and immediately, which would put unnecessary load on the system, syncs are bundled and run at fixed times. For day-to-day operations, this means overall: more reliability, less manual rework and a system that takes care of routine tasks on its own instead of having to react on demand.",[14,36,38],{"id":37},"frequently-asked-questions","Frequently asked questions",[10,40,41,45,48,49,52,54,55,58,60,61],{},[42,43,44],"strong",{},"Why doesn't some data appear in 1Tool immediately?",[46,47],"br",{},"\nBecause certain processes, such as the bank sync via finAPI, run at fixed, recurring times rather than being triggered immediately with every single change.\n",[42,50,51],{},"How often do the automatic parser processes run?",[46,53],{},"\nThe parser processes for tickets, costs, emails, projects and leads, among others, run every five minutes.\n",[42,56,57],{},"How often does the system check whether a time-based automation needs to run?",[46,59],{},"\nA dedicated process checks every single minute whether a scheduled automation is due.\n",[42,62,63],{},"Would you like to see which background processes can take work off your hands in everyday operations?",[14,65,67],{"id":66},"read-more","Read more",[69,70,71],"ul",{},[72,73,74],"li",{},[75,76,78],"a",{"href":77},"\u002Fen\u002Fblog\u002Fai-agents-automated-document-processing\u002F","AI agents behind the scenes: automated document processing",[10,80,81],{},[75,82,84],{"href":83},"\u002Fen\u002Fappointment-request\u002F","Book a demo",[14,86,67],{"id":87},"read-more-1",[69,89,90,96],{},[72,91,92],{},[75,93,95],{"href":94},"\u002Fen\u002Fblog\u002F1tool-api-documentation-openapi-live\u002F","The 1Tool API: more than 2,500 endpoints, documented live",[72,97,98],{},[75,99,101],{"href":100},"\u002Fen\u002Fblog\u002Fwebsocket-infrastructure-real-time-1tool\u002F","Real-time updates without detours: the WebSocket infrastructure behind 1Tool",{"title":103,"searchDepth":104,"depth":104,"links":105},"",2,[106,107,108,109,110,111],{"id":16,"depth":104,"text":17},{"id":23,"depth":104,"text":24},{"id":30,"depth":104,"text":31},{"id":37,"depth":104,"text":38},{"id":66,"depth":104,"text":67},{"id":87,"depth":104,"text":67},[113],3330,"2026-07-03T09:00:00",false,null,"md","\u002Fmedia\u002F2026\u002F07\u002Fhintergrundjobs-warteschlangen-1tool.jpg","en",{},"2026-07-25T08:26:28",true,"\u002Fen\u002Fblog\u002Fbackground-jobs-queues-1tool",{"title":5,"description":12},"How 1Tool works in the background: queues, scheduled processes and automated clean-up jobs behind the interface.","Background jobs and queues: how 1Tool works","background-jobs-queues-1tool","\u002Fen\u002Fblog\u002Fbackground-jobs-queues-1tool\u002F","en\u002Fblog\u002Fbackground-jobs-queues-1tool","posts","52K6NPAsRxkZxFDWxLrnMhFtnQxWZ1m7znccy6aYo7c",1791582059446]