Hey guys!
I just build a crew, and it works OK on my local computer.
However, after uploading it on Github and deploying on CrewAI Enterprise, even with a successful deploy and the crew is online with API URL and Bearer Token and such, but in the Run tab, it said " Crew not available Crew not found or unavailable."
I tried to re-deploy several times but still the same error.
I have the same issue. did you find a fix?
Unfortunately, not yet. I tried to re-run it several times as it already expired due to no activity. And today, the status becomes failed. I will try to delete and re-deploy later.
I am also facing same issue. Any resolution or fix on this issue ?
I get this alot.
For me it is due to a number of things.
- changing the way you call the crew
- sometimes too many crews.
- API Passcode for OpenAI etc not correct
- sometimes… unknown
Sadly there are no logs we can see, so i recommend simplifying the crew and slowly adding features till it stops working.
I know the amazing CrewAI team are working on this… so soon it will be easier
TLDR : If a crew works on your system does not mean it will work in Enterprise.
Hi y’all! We’re updating our enterprise suite to make this better. Did you all try re-deploying the app? If so, did you still get the same error after deployment was done and crew shows as online?
Any info and details will help. Also if you could share your deployment ID so I can look into it? (it should be in the url of the crew)
1 Like
In my case, I changed the import path of the custom_tool module from the relative path to the absolute path, so it worked normally.
Since debugging was not possible in the enterprise app, the cause was found by gradually expanding the modules of agent and tool in the initial stage.
There seem to be various causes for the “crewis online but not available” situation. It would be nice if I could check the detailed log.