Viewing Active Executions

Hello Kalvin.

We have the HTTP Request Tool node, which allows you to call any API. Please see this link for more details:

And this post contains an example using the node:

Best.

Yes, I've utilized hundreds of HTTP request nodes. The challenge is that there isn't an endpoint available to retrieve currently running executions.

Ok, in this case, is this endpoint within callin.io or somewhere else?

I've noticed discussions on the callin.io community forum regarding the callin.io endpoint /rest/executions, but it appears to be non-functional. This might be due to deprecation, as it was an undocumented feature.

Therefore, I'm inquiring about the current methods for retrieving a list of executions via API.

Could you please share how others are currently accessing this information?

My apologies, I'm unsure of the current location of this endpoint at this time.

Take a look at this:

• callin.io | callin.io Docs
• callin.io public REST API Documentation and Guides | callin.io Docs
• API reference | callin.io Docs

There is also another execution status available – queued. Source: feat(editor): Show new executions as
Queued
in the UI, until they actually start by netroy · Pull Request #10204 · callin.io-io/callin.io · GitHub

If this answers your question, please mark this post as a

Solution.

Hi, I believe this is simply part of the architecture, likely to accommodate both worker and non-worker scenarios. From what I can tell, the API only provides 'failed', 'completed', and 'waiting' states for filtering. This is probably because callin.io polls the queue state periodically (with a default of 20 seconds) and cannot directly know when workers pick up tasks. However, the workers do track their status through the database. Full execution details are accessible directly from the database itself.

'New' likely signifies a task waiting in the queue, while 'Running' indicates a worker has picked it up.

image1855×678 78.4 KB

I don't think it's intended for direct use like this, but if you require it, feel free to access the database directly, assuming you are using a self-hosted setup.

BTW, if the objective is simply to ascertain the number of active workflows without identifying them, you can activate queue mode with workers and monitor queue metrics (also self-hosted):

• Active
• Waiting

Enable Prometheus metrics | callin.io Docs

Yes, I've reviewed all the provided resources, but unfortunately, none of them address the specific issue I'm encountering.

This looks good… I’ll explore how I can utilize the database practically without an API… perhaps by developing my own API on the server.

Let me explain the objective:

There are instances where I prefer not to execute a workflow if it's already in progress. This is to mitigate potential API throttling or other problems that arise when multiple workers execute the same code, affecting the same data.

Hi, have you considered using a toggle flag in an external system? You could set it when the process starts and then clear it upon completion or if an error occurs. This approach avoids over-engineering.

Yes, I attempted managing this in Google Sheets, but it became cumbersome to add a Google Sheets read node and an IF node for each individual workflow within the main workflow. I suppose it would be less of a hassle if I only had to do this in the single main workflow, but I prefer to run the sub-workflows independently at times. That's why I was hoping for a more streamlined approach overall.

Perhaps a feature request would be beneficial. The ability to toggle a setting, such as “Maximum X concurrent executions,” would be useful. This would allow the system to check before scheduling.