I have tested the same URL here and was able to get results with no problems. Can you check if your login credentials are correct and try again?

My credentials were set and saved and had been running for months with no problem. I also tried to input them again, save and run, and it's still returning 0 results for me. I tried to login to Upwork manually using the same credentials and secret word and I logged in with no problems, so I'm confident the credentials are correct (they were copied and pasted). I tried updating the proxy and that didn't work still returned 0 results. Any idea how to proceed?

The problem still persists, I have again tried to login manually using the credentials with no problems, and have updated them again in the actor both on the saved runs and tried running it manually, here is the run ID: 62mV7tSWMZA2BDGrz - it's saying in the logs it's having a problem with the security question which I know is correct. I noticed that this pops up when I enter the security question (image attached), and I wonder if this is causing problems. i.e. the question is OK, but when this box pops up the script isn't handling it?

Looking at the logs, it seems like the page didn't return any results for you but when I try it it is working. The pop-up and your credentials should not be a problem since the logs say that the scraper started looking for jobs. I have added more debug logs in a beta version of the scraper, can you run it once and share the run ID again so I can check if your run triggers a specific part of the code? Should be version 1.7.6.

Thanks, here is the latest run ID, using beta: UbZkKWUIIjdw1X5M6

Still the same. Is this happening just for one URL or all your runs are like this?

I normally just run one URL everyday, and until a few days ago it worked. I check it every morning and it's the actor that most consistently returns the results.

I did just try a new URL to test (here is the run ID: Herz7e9iy17ZgR5HI) and again the actor returns 0 results for this URL as well.

Anything else I can try?

Can you try without providing the login credentials? It will probably not return all the data but at least we will know if this is happening for your user only.

Tried without the credentials with the same URL, here is the RUN ID: s5qrzZi4RhRqiJUfX

Returned three results - requested 100 but I appreciate it wasn't going to give this to me.

I tried logging in using different Upwork credentials and faced the same problem of returning 0 records; here is the run ID: KdeQbQyOz3QMiCXPK

Is there anything else I can try on this? Really keen to get it back up and going as it forms an important part of my workflow.

Let me know if there are any other settings I can try, or anything else I can provide.

I am testing some improvements to see if I can fix this issue. It is a bit difficult since I am not able to replicate it on my side. I will let you know once I have a new beta version for you to try. I am almost done with it.

I think I have found the issue. Can you try with the latest build (v1.7.8)?

Unfortunately still returning 0 results; I have tried two runs logging in with two different Upwork accounts to see if that was the problem; here are the run IDs:

vvA9o9NbZTrXhUGtu 1bv3mlbivFwS7pTF3

I have also created a Loom so you can see all my settings in case there is something you can't see in the logs or from the run ID:

https://www.loom.com/share/7b943c16be254e219833bf7b1db67e38

I appreciate the effort you're putting in to try and fix this

I don't see anything wrong with your settings. I have also tried with the same settings but for me works every time. I have made another beta release, this time it will take a screenshot if no jobs are found. Can you please run it and share the run ID so we can see what is going on?

Thank you - here is the run ID when I have used 1.7.9:

ioYxlRKxVOOrmKVcD

Let me know if there's anything else I can run and try.

If there's anything else I can do, or try, please let me know.

Sorry for not responding early. I looked into the screenshots and the page was loaded with all the data. I will reach to Apify support to see if they can help me replicate your run and try to figure it out why you have no results.

Awesome, thanks. Looking forward to resolving the problem :)

I have release a new beta version, can you give it another try?

Thanks, Gustavo, I tried running the Beta version, 1.7.10, here is the run ID: AEpoMtWqPHCfAnvBf

Still returning 0 results, unfortunately, but the error messages in the log do look a little different to before, so perhaps some clues in that.

Yes, I have deployed a new beta version that might fix the issue. Can you check it out?

Tried running the beta and it failed - Ha2oQsd9eJzyNWkYD - said there was an exception that was not handled, and it aborted itself.

This is the exact error message: There was an uncaught exception during the run of the Actor and it was not handled.

I tried running it again with the same result: 8hC9a2jE2GXvxTdKS

I tried running 1.7.12, just to see, with the same result: FekBtanePpsiSpgL9

It seems like an internal error from Apify but I have never seen it before, even with v1.7.12. The error message says that there might be a misconfiguration in the crawler. Can you try to reset your input to default values and run it once to see if the same error happens?

There is a button at the right since of the save input button for that.

I tried resetting and running, and got the same error message - tried it twice:

Yd7PZoKTLONLcREku

Cavk51Uc7sVTScNfT

Apify support told me to update my actor. Can you try the new beta version?

Actually wait a bit more.

Can you try it?

Tried using the new 1.7.15 - Uf9GBZTvT5KifNiQH - There was an uncaught exception during the run of the Actor and it was not handled. Tried resetting all values to default, redoing them and using 1.7.15 - wRCCw6RrU54KlPVtn - There was an uncaught exception during the run of the Actor and it was not handled.

Can you schedule a meeting with me so we can go over your issue in more detail? You can do that here: https://calendly.com/gustavorudiger

Awesome, done for tomororw, thanks!

I think now it will work, and it is faster!

Anddd I now have results :) - thank you.

Only one problem now, I noticed that on the first page it scraped all of the results twice.

So when I asked for 50 I got 40 as the first page was duplicated.

It runs very quickly though!

Run ID if you want to see the result: STAxYqfsVncjGsmQy

Nice, I have deployed a fix for the duplicated results.

Just tested - first 10 results still duplicated using the latest actor: 4486x3eNuRvgX3oI7