Watch address from code is not working

Moralis General
#1

Screenshot 2022-02-14 at 15.02.47
Screenshot 2022-02-14 at 15.02.472880×930 426 KB

My code snippet-

const results = await Moralis.Cloud.run(
            "watchBscAddress",
            {
                address: address,
                sync_historical: false,
            },
            { useMasterKey: true }
        );

Getting this error in console

Screenshot 2022-02-14 at 15.04.42

#2

checking now, I know that your particular case is with a testnet server

#3

It works fine for me on testnet, what is your server url?

I used this syntax

    const results = await Moralis.Cloud.run("watchBscAddress", {address: "asdfasdf", syncHistorical: true}, {useMasterKey: true})
#4

My server url- https://k84qr0r6ywbq.usemoralis.com:2053/server

#5

can you try again now? I already added an address sync on bsc on your server with watchBscAddress

#6

Not working for me.

How did you manage to add an address?

#7

I used this code:



x = async () => {
    const  Moralis = require('moralis/node')
    console.log(Moralis.CoreManager.get("VERSION"))
    await Moralis.start({ serverUrl: "https://k84qr0r6ywbq.usemoralis.com:2053/server", appId: "asfdsafsdf", masterKey: "afasfsdf" });

    const results = await Moralis.Cloud.run("watchBscAddress", {address: "adsadfasdf", syncHistorical: true}, {useMasterKey: true})
    console.log(results)

    }

x();

From logs it doesn’t look like you tried after I said to try again

#8

I tried but it isn’t working. I signed up on Moralis from a different email and created another server there. Tried to run it on that, but it still doesn’t work for me

#9

I just tried running your code in my terminal. Still same issue-

Screenshot 2022-02-14 at 15.57.47
Screenshot 2022-02-14 at 15.57.472770×762 285 KB

#10

What result do you get from console.log(Moralis.CoreManager.get("VERSION"));? Which version do you have?

#11

checking, now it looks like it doesn’t work for me either

#12

Any idea what may be the issue?

#13

I don’t know exactly yet, we will investigate

#14

the problem should be fixed now if you update the server to latest version