Timeout error on attempting to pull costs

[adyoull]

Octopus website is working fine and I've changed manually to Agile as I know that was cheaper today due to negative pricing and charging my car in that period.

But received this error:

Octobot v0.7.2 on. Initiating comparison in 5.3 minutes

Traceback (most recent call last):

  File "/usr/local/lib/python3.9/site-packages/anyio/_core/_tasks.py", line 115, in fail_after

    yield cancel_scope

  File "/usr/local/lib/python3.9/site-packages/gql/client.py", line 1537, in _execute

    result = await self.transport.execute(

  File "/usr/local/lib/python3.9/site-packages/gql/transport/aiohttp.py", line 308, in execute

    async with self.session.post(self.url, ssl=self.ssl, **post_args) as resp:

  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 1425, in __aenter__

    self._resp: _RetType = await self._coro

  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 730, in _request

    await resp.start(conn)

  File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1059, in start

    message, payload = await protocol.read()  # type: ignore[union-attr]

  File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 671, in read

    await self._waiter

asyncio.exceptions.CancelledError: Cancelled by cancel scope 78f38a164ac0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "/app/main.py", line 380, in run_tariff_compare

    setup_gql(get_token())

  File "/app/main.py", line 216, in get_token

    result = client.execute(query)

  File "/usr/local/lib/python3.9/site-packages/gql/client.py", line 469, in execute

    data = loop.run_until_complete(

  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete

    return future.result()

  File "/usr/local/lib/python3.9/site-packages/gql/client.py", line 367, in execute_async

    return await session.execute(

  File "/usr/local/lib/python3.9/site-packages/gql/client.py", line 1628, in execute

    result = await self._execute(

  File "/usr/local/lib/python3.9/site-packages/gql/client.py", line 1537, in _execute

    result = await self.transport.execute(

  File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__

    self.gen.throw(typ, value, traceback)

  File "/usr/local/lib/python3.9/site-packages/anyio/_core/_tasks.py", line 118, in fail_after

    raise TimeoutError

�
TimeoutError

[m477r1x]

Can confirm I'm also experiencing this. I'm wondering if it's due in part to the fact that they have changed the Go sign-up page, since you can now select variable or fixed go tariffs on the page

[adyoull]

Can confirm I'm also experiencing this. I'm wondering if it's due in part to the fact that they have changed the Go sign-up page, since you can now select variable or fixed go tariffs on the page

I see they've introduced a £25 fee to exit Octopus Go Fixed aswell, probably to deter tariff hopping.

[m477r1x]

Can confirm I'm also experiencing this. I'm wondering if it's due in part to the fact that they have changed the Go sign-up page, since you can now select variable or fixed go tariffs on the page

I see they've introduced a £25 fee to exit Octopus Go Fixed aswell, probably to deter tariff hopping.

Yeah I noticed that, so I chose the flexible one when I switched manually yesterday after the script failed lol

[curator8888]

I got the same error but I was on Agile and Agile was still my cheapest, so I stayed but I still got the error.

[eelmafia]

Can anyone confirm if this is still happening?

[m477r1x]

Can anyone confirm if this is still happening?

My output from 2 nights ago

MinMaxOctopusBot  | Initiating Switch to GO
MinMaxOctopusBot  | Traceback (most recent call last):
MinMaxOctopusBot  |   File "/app/main.py", line 324, in run_tariff_compare
MinMaxOctopusBot  |     compare_and_switch()
MinMaxOctopusBot  |   File "/app/main.py", line 305, in compare_and_switch
MinMaxOctopusBot  |     switch_tariff(opposite_tariff[curr_tariff])
MinMaxOctopusBot  |   File "/app/main.py", line 253, in switch_tariff
MinMaxOctopusBot  |     page.locator("section").filter(has_text="Already have a SMETS2 or “").get_by_role("button").click()
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/sync_api/_generated.py", line 15450, in click
MinMaxOctopusBot  |     self._sync(
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/_impl/_sync_base.py", line 115, in _sync
MinMaxOctopusBot  |     return task.result()
MinMaxOctopusBot  |            ^^^^^^^^^^^^^
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/_impl/_locator.py", line 156, in click
MinMaxOctopusBot  |     return await self._frame.click(self._selector, strict=True, **params)
MinMaxOctopusBot  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/_impl/_frame.py", line 488, in click
MinMaxOctopusBot  |     await self._channel.send("click", locals_to_params(locals()))
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/_impl/_connection.py", line 61, in send
MinMaxOctopusBot  |     return await self._connection.wrap_api_call(
MinMaxOctopusBot  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
MinMaxOctopusBot  |   File "/usr/local/lib/python3.12/dist-packages/playwright/_impl/_connection.py", line 528, in wrap_api_call
MinMaxOctopusBot  |     raise rewrite_error(error, f"{parsed_st['apiName']}: {error}") from None
MinMaxOctopusBot  | playwright._impl._errors.TimeoutError: Locator.click: Timeout 30000ms exceeded.
MinMaxOctopusBot  | Call log:
MinMaxOctopusBot  |   - waiting for locator("section").filter(has_text="Already have a SMETS2 or “").get_by_role("button")

[adyoull]

Since I've had octopus manually move me over again I've not had this issue

[m477r1x]

Since I've had octopus manually move me over again I've not had this issue

Move you over from which tariff to which tariff? I am able to reliably replicate the issue every time when switching from Agile to Go. However switching from Go to Agile still works fine. So if octopus manually switched you to go, and then the script switched you back to agile and hasn't attempted to switch you back to Go again since, then you wouldn't be seeing the error and it might look like it is resolved when actually the script just hasn't tried to switch you to Go again since.

[adyoull]

Since I've had octopus manually move me over again I've not had this issue

Move you over from which tariff to which tariff? I am able to reliably replicate the issue every time when switching from Agile to Go. However switching from Go to Agile still works fine. So if octopus manually switched you to go, and then the script switched you back to agile and hasn't attempted to switch you back to Go again since, then you wouldn't be seeing the error and it might look like it is resolved when actually the script just hasn't tried to switch you to Go again since.

They've moved me once to Go from agile and I've successfully changed back automatically via the script since from go to agile and back here's my switches

[joeShuff]

@m477r1x Based on your error your version is quite out of date. It's still using the browser automation instead of the API.

Please can you pull the new version as that will likely fix your issues.

[m477r1x]

Correct @adyoull thats exactly what I suspected. The script works currently to transfer from Go to Agile, but won't work to transfer from Agile to Go. I can guarantee the next time the script attempts to transfer from Agile to Go, rather than it being done manually, you will get the error.

It's due to the change in the way Go is now being set up by octopus, there's 2 types. Go fixed and Go variable. So the web page for sign up has changed, and potentially the API calls as well.

[adyoull]

Correct @adyoull thats exactly what I suspected. The script works currently to transfer from Go to Agile, but won't work to transfer from Agile to Go. I can guarantee the next time the script attempts to transfer from Agile to Go, rather than it being done manually, you will get the error.

It's due to the change in the way Go is now being set up by octopus, there's 2 types. Go fixed and Go variable. So the web page for sign up has changed, and potentially the API calls as well.

It has successfully changed me back to go from agile as per below just yesterday, when octopus had to intervene was a couple of weeks ago

[m477r1x]

@m477r1x Based on your error your version is quite out of date. It's still using the browser automation instead of the API.

Please can you pull the new version as that will likely fix your issues.

@joeShuff I will pull the latest version tonight. I guess I wasn't picky enough in checking the error, to my eye it looked the same as the other errors in these issues.

[joeShuff]

You're right that they're both timeout errors, but yours is a timeout looking for a component on the browser whereas the reported issue is an API timeout.

The browser hasn't been used in a while and the issue you are seeing was resolved by the removal of the browser element.

[m477r1x]

@joeShuff have just pulled the latest version. It was my bad I guess, I did look through the release notes of the recent releases when i first encountered the error, but i coudln't see anything which obviously addressed it. Had I realised there had been such a major change as removing the UI part of the script i would have updated. So am I right in assuming that now there is no such thing as the playwright stuff in there anymore?