When calling a domain for the first time from a skill it works, second and more timee does not work. Very strange but also deterministic. The domain and url is reachable. Direct call is working. Call from skill only at first time. Domain is in network allow list.
Hey @r.napierski, that does sound confusing especially since the first call works fine.
With Hosted Shell in the mix, this usually isn’t the allow list itself. If the first call succeeds, the domain is reachable. The pattern you’re seeing tends to come from what happens after:
- shell runs are stateless, so anything relying on session, cookies, or prior context won’t carry over
- follow-up calls can fail if the tool output or command chaining isn’t returned in the expected format
- timeouts or 429/5xx responses on the second call can cause it to stop retrying
A few quick things that have helped others:
- compare first vs second call in your server logs (headers, auth, payload)
- check if the second call is slower or hitting a timeout
- confirm you’re not relying on cookies or custom headers between calls
- inspect the exact shell command/output being passed back on the second run
Not ideal, agreed but this pattern is usually pretty deterministic once you spot the difference in call #2.
If you can share what the second call returns (status or logs), that should narrow it down fast.
-Mark G