I run a lot of workflows via API, and I recently noticed that some start and hang indefinitely. When I go to the gumloop workflow, I see this error message: “You have exceeded the credit limit this month for your subscription. You can enable credit overage in your profile settings.”. This is a serious problem where my production application thinks the workflow is running and is awaiting a response, instead of immediately getting a 422 or 429 error indicating that gumloop is unable to run the workflow because of lack of credits. If there was such a mechanism, I would put alerts in place and get reminders to purchase more credits.
Hey @mahammad - When you see this error on your run, the State would indicate FAILED in the response body: https://docs.gumloop.com/api-reference/running-an-automation/retrieve-run-details#response-state
And you can view the complete logs as well: https://docs.gumloop.com/api-reference/running-an-automation/retrieve-run-details#response-log
You can see an example output with your failed run here: https://docs.gumloop.com/api-reference/running-an-automation/retrieve-run-details?playground=open#response-log
Can you use that to put alerts in place?
Hey Wasay, thanks for your reply! We don’t use the retrieve-run-details API because the workflows can take variable amount of time. I’ve built my workflows to send a api callback to our servers with the job result & payload.
I guess I could add a check to the api you mentioned after starting the workflow, but sending an error response if there are no credits is a standard practice, so wondering if you have that on the roadmap.
That makes sense. We can add this to our roadmap.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.