No server function matching "*" has been registered

[anvil3]

I register 3 functions with uplink (from two different servers)

I see it in the output :

And then when my background function runs that tries to call that server callable, it fails with
No server function matching … has been registered

What am I doing wrong?

I can’t seem to have luck with this since a few days ago, I’ve been raising and shutting down uplinks a lot, so maybe I overpowered the disconnect system?

I read somewhere that the uplinks are load balanced between the different registered service, maybe I was wrong and that’s not really the case anymore so one of my servers kicks the other one out?

[p.colbert]

Could this be relevant in your case? Anvil Docs | Deployment Environments

[anvil3]

Could be, are you referring to this?

I disabled “allow uplink to be called from other environments”

Does this mean that from dev I won’t be able to call uplinks that have registered with the published version?

[p.colbert]

That’s how I read it.

You can have Anvil give other environments their own Uplink codes. This may be useful, for example, if you’re rewriting some Uplink code, and don’t want the Production version to be affected during the rewrite/edit/test/debug phase.

[anvil3]

Banging my head against this, is there no way to call staging anvil functions from repl?

@meredydd ?

I’m running a repl while being on staging, trying to launch a server function and repl says that remove call is not registered, but it is, just on staging.

Do I really have to configure staging to "receive’ webhooks form other environments? In which case my prod things will send calls to my staging as well and then all kinds of mess will happen?

[patricia]

The REPL connects to your Debug Environment. If you want to call uplink functions, the uplink will need to either be connected to your development environment, or configured to allow calls from other environments.

Being able to choose which environment a server REPL should connect to would be great, so I’d recommend creating a Feature Request thread and I’ll add it to our internal list as well!