cookin2 wrote:

MdRafique182014 wrote: Hi my family members

Hey bro ... Wonder where Hamsou is?

I got 1 hit this afternoon. I was refreshing at 7 seconds and it was too fast so I got the requested too many times thing. After an hour + I tried to refresh to get a hit, but when I did it said that I had already done it ...

You too ? This is crazy ! Someone is hijacking our assignments lol !

At least you are lucky, you got this on an oops and not in the middle of doing a hit,
Interesting. Are they cutting corners now and sharing hits ? Once a hit has filled slots
it voids itself ? Sounds like cost cutting measures. Before, the moment you open
a HIT your slot was guaranteed, reserved, now they seem to be share / splitting,
sort of like ads on a PTC that can expire whilst you view them
If this is the case then this is very VERY bad.

cookin2 wrote:

MdRafique182014 wrote: Hi my family members

Hey bro ... Wonder where Hamsou is?

I think he is busy today

Darkstar2 wrote:

cookin2 wrote:

MdRafique182014 wrote: Hi my family members

Hey bro ... Wonder where Hamsou is?

I got 1 hit this afternoon. I was refreshing at 7 seconds and it was too fast so I got the requested too many times thing. After an hour + I tried to refresh to get a hit, but when I did it said that I had already done it ...

You too ? This is crazy ! Someone is hijacking our assignments lol !

At least you are lucky, you got this on an oops and not in the middle of doing a hit,
Interesting. Are they cutting corners now and sharing hits ? Once a hit has filled slots
it voids itself ? Sounds like cost cutting measures. Before, the moment you open
a HIT your slot was guaranteed, reserved, now they seem to be share / splitting,
sort of like ads on a PTC that can expire whilst you view them
If this is the case then this is very VERY bad.

I can't figure out what they're doing, but I don't like it. They have changed something -

~~~~~~~~~~~~~

MdR - our family member might be busy, but I saw him peek in

cookin2 wrote:

MdRafique182014 wrote: Hi my family members

Hey bro ... Wonder where Hamsou is?

I got 1 hit this afternoon. I was refreshing at 7 seconds and it was too fast so I got the requested too many times thing. After an hour + I tried to refresh to get a hit, but when I did it said that I had already done it ...

Hi! cookin2 & MDR & all family members

The time intervals doesn't matter what matter is to keep an eye on the system erros behavior .. if you got a hit & instantly turns to an error then you have to refresh manually to control the 4 tries you have .. what happens is that the page that contains the word "step" turns to an error before the extension can check for it .. so it continue refreshing .. then too requested.

Lets say if I got a hit & the system turns the error but not instantly then the refresher will stop .. time intervals doesn't matter 5 7 or 10 secs.

& since assign links are recycled then the first worker submitting a hit will win & the other one wil get "invald state" when he try to refresh his terminal.

Oops just converted to a HIT but again - "We're sorry, but something went wrong" in the terminal. *sob* *sob*

And now, connection lost. What the..

vorabhargav wrote: Oops just converted to a HIT but again - "We're sorry, but something went wrong" in the terminal. *sob* *sob*

And now, connection lost. What the..

The green error ? That was probably a GitLub training hit, when that happens wait it out.
I had this happen before, it usually works, try refreshing the page in terminal
after a while and it should work.

About the connection lost yeah, I think they are now share-splitting the hits, I think a cost cutting measure to relieve their VM Stack, but this could potentially mean people being cut off in the middle of hits when the slots are filled.
I hope this is temporary.

If this keeps up I will write to RF. Today I lost 28 steps because of this connection error.

I know that today they had several outages to their hosting (tester.rainforestqa) got some intermittent outage, and they also had partial outages to their provider for screenshots.....So maybe this is why we are getting
connection errors in middle of hits......... I think they patched something, if you close a HIT window, its session no longer remains "floating" and is marked as abandonned (but since they replaced all errors with completed) that might be a good theory. The floating session was a glitch.

hamsou73 wrote:

cookin2 wrote:

MdRafique182014 wrote: Hi my family members

Hey bro ... Wonder where Hamsou is?

I got 1 hit this afternoon. I was refreshing at 7 seconds and it was too fast so I got the requested too many times thing. After an hour + I tried to refresh to get a hit, but when I did it said that I had already done it ...

Hi! cookin2 & MDR & all family members

The time intervals doesn't matter what matter is to keep an eye on the system erros behavior .. if you got a hit & instantly turns to an error then you have to refresh manually to control the 4 tries you have .. what happens is that the page that contains the word "step" turns to an error before the extension can check for it .. so it continue refreshing .. then too requested.

Lets say if I got a hit & the system turns the error but not instantly then the refresher will stop .. time intervals doesn't matter 5 7 or 10 secs.

I know exactly what you mean!! You're a good explainer Thank you

The only thing is that I can refresh with the extension a lot more than 4 times and still have it turn into a successful hit. That just happened, in fact. I was refreshing before I came here to post (few seconds probably). I just finished a 9 step GH. How did people figure out that 4 was the max?

Yup, the GitHub one... I refreshed and it did mend itself! So far, so good. But I was almost at step 4 when suddenly it showed "Connection lost". Had to refresh, restart the Hit.

This one was okay, as it was a small one (Training ones). But imagine if we got such issues for client sites - imagine vendorIQ! or any other, like you faced.

So what you explained is indeed true.

Canuckmom1 wrote:

try to type it
if it doesnt work, report it

good morning RF family

I got few githubs from the latest ID

coated_pill wrote: good morning RF family

I got few githubs from the latest ID

Good morning

So glad you at least got a couple hits

application error

MdRafique182014 wrote: application error

same here

MdRafique182014 wrote: application error

Same here.. I'm going to sleep now, really exhausted. The terminal is also so slow today...

same here as well and good morning

vorabhargav wrote: Yup, the GitHub one... I refreshed and it did mend itself! So far, so good. But I was almost at step 4 when suddenly it showed "Connection lost". Had to refresh, restart the Hit.

This one was okay, as it was a small one (Training ones). But imagine if we got such issues for client sites - imagine vendorIQ! or any other, like you faced.

So what you explained is indeed true.

They would be losing clients if this is the case.

I think the connection lost in middle of hits today is due to intermittent outages to the
tester.rainforest ......

To cookin2: How did people know 4 was limit is simple, RF used to post jobs under 4 or 5 or more JOB IDs at the same time, under test a web application I, II, III, IIII, IIIII, etc. you could open multiple windows and do 4+ hits at once back in the days......since each task was technically a different section - each task had different TYPE of jobs.
I'm pretty sure the limit was higher than 4 - I've seen 6 JOB IDs at one point when RF was very busy, and remember doing 6 at once. I don't think they had a limit back. I think this limit got reduced as they decreased their number of hits, clients, or whatever. More workers, fewer hits = they have to reduce limits which is normal !

Regarding limit to refreshing oops, it's probably based on age of assignment link or other factors.
I don't see each assignment link have its own timer, I'm sure they are using some sort of balancing
based on amount of work in the system. lower work, stricter limits, high work volume, higher limits.

I am cycling between something went wrong and application error now.

MdRafique182014 wrote: application error

I just got the green box of death - we're sorry ... etc

cookin2 wrote:

MdRafique182014 wrote: application error

I just got the green box of death - we're sorry ... etc

Wait it out, try refreshing page after a while, it usually works.
Since those are small hits, you might as well make good use of the 60 min and wait,
nearly 100% of the times I had this, it resolved on its own and could complete hit.