I’m planning a Busabase workflow that processes records matching certain conditions. Sometimes there may be nothing to process, which would be expected. How should that case be handled? How can I distinguish a successful run with no matching records from a failed query or incorrectly configured conditions?
If the query actually ran and found zero matching records, I would treat that as a successful empty result, not a failure. A failed query, missing access, or an unexpectedly broad/narrow filter is a different outcome. Keep the search conditions, time, number of matches and any error alongside the result, so a reviewer can tell them apart.
There is one important Busabase boundary today: the Workflow canvas saves the process design but does not run it on its own, so it cannot currently produce a built-in “successful run with zero matches” status for that canvas. If an Agent or another connected runner carries out these steps, ask it to report one of three results: completed, 0 matches; completed, N matches; or failed before a reliable count was available. For a recurring job, define what zero usually means and flag it for review only when zero is unexpected. We have recorded the need for distinct run outcomes when executable workflows are available. Is zero a normal result for your filter, or a sign that something probably went wrong?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in