wW
Apify & Crawlee5w ago
2 replies
w

The issue with the openrouter actor has been going on for four days...

General
Hey team, I found that openrouter actor does not start correctly and the error is as follows:
2026-01-15T06:45:21.569Z ACTOR: Pulling container image of build 2xhHb8Fpd4dy4wiuj from registry.
2026-01-15T06:45:21.572Z ACTOR: Creating container.
2026-01-15T06:45:23.025Z ACTOR: Starting container.
2026-01-15T06:45:25.083Z INFO  System info {"apifyVersion":"3.5.2","apifyClientVersion":"2.20.0","crawleeVersion":"3.15.3","osType":"Linux","nodeVersion":"v22.21.1"}
2026-01-15T06:45:25.090Z [Charging] Initialized charging manager {
2026-01-15T06:45:25.092Z   maxTotalChargeUsd: 4.949591,
2026-01-15T06:45:25.094Z   pricingInfo: {
2026-01-15T06:45:25.096Z     pricingModel: 'PAY_PER_EVENT',
2026-01-15T06:45:25.098Z     isPayPerEvent: true,
2026-01-15T06:45:25.100Z     maxTotalChargeUsd: 4.949591,
2026-01-15T06:45:25.102Z     perEventPrices: {
2026-01-15T06:45:25.104Z       'openrouter-api-usage': 0.001,
2026-01-15T06:45:25.106Z       'apify-actor-start': 0.01,
2026-01-15T06:45:25.108Z       'openrouter-api-usage-micro': 0.0001
2026-01-15T06:45:25.110Z     }
2026-01-15T06:45:25.112Z   }
2026-01-15T06:45:25.114Z }
2026-01-15T06:45:25.227Z INFO  [Status message]: Unexpected issue occurred. Please contact support.
2026-01-15T06:45:25.717Z ACTOR: Actor Standby server was idle for too long, finishing run.
2026-01-15T06:45:25.719Z ACTOR: Actor run will be killed gracefully. It has 30 seconds to persist state.
2026-01-15T06:45:25.721Z ACTOR: Notifying Actor process about persisting state.
2026-01-15T06:45:40.718Z ACTOR: Sending SIGTERM signal to container.

what can i do?
It still doesn't seem to work. It was the same during testing today...

response body context:
{
  "error": {
    "type": "failed-to-choose-actor-run",
    "message": "Failed to choose an Actor run for the request. Please make sure that Actor runs are not failing in the Apify Console."
  }
}
Was this page helpful?