runwayml/hosted-models

Interact with Runway Hosted Models with only a few lines of code!

hosted-models's Issues

Inactive hosted model can't be woken up, 404s my request

This is similar to #3 but I see that one was closed because the user had a $0 balance. In my case I only have a single hosted model, in the unsubscribed mode. It set itself to inactive, and hovering over the status says:

Leading me to believe instantiating the model and calling waitUntilAwake would kick it into gear. However, any attempt to instantiate the model fails with:

Unhandled error during request: Error: Model not found. Make sure the url is correct and that the model is "active".
  at new NotFoundError (/vercel/workpath0/node_modules/@runwayml/hosted-models/build/HTTPErrors.js:38:23)
  at HostedModel.<anonymous> (/vercel/workpath0/node_modules/@runwayml/hosted-models/build/HostedModel.js:230:39)

So, how can I programmatically wake a model up???

Instantiating and/or querying the model results in 404

Hey there. Not sure if this is a bug in the JS library, Runway's backend, or if I'm getting silently rate-limited— so please let me know if there is a better place to post this!

My app encounters a PermissionDeniedError (as defined in src/HTTPErrors.ts:23) with the message 'Model not found. Make sure the url is correct and that the model is "active".' The API key is valid.

The network activity shows failures (404) for:

• GET https://MODEL-NAME.hosted-models.runwayml.cloud/v1/
• POST https://MODEL-NAME.hosted-models.runwayml.cloud/v1/query

Using waitUntilAwake makes no difference, as that call will fail, too.

Every time I encounter this error, I find that the hosted model has become Inactive, as shown on the dashboard at https://app.runwayml.com/hosted-models. I can then toggle it to Active, and perhaps make 1 request through my app before the model is once again Inactive.

This behavior makes me think there might be either a backend issue or some kind of rate-limiting. For reference, I have been making around 50-60 requests/hour while testing. If rate-limiting is the case here, it would be nice if the model returned 429 Too Many Requests instead of silently inactivating.