Skip to content

Timeout in user defined handler should cause retry #907

Closed

Description

@Pijukatel

Timeouts in user defined handlers should be treated the same way as other exceptions raised from within the user handler.
This should cause retry.

Currently the request that times out will end up in strange state in RequestQueue and it will block crawler from closing for 300 secs until following triggers:
"The request queue seems to be stuck for 300.0s, resetting internal state."

(Regarding blocking sync code timeouts from user defined handlers: #908)

Activity

  1. added
    bugSomething isn't working.
    t-toolingIssues with this label are in the ownership of the tooling team.
    on Jan 15, 2025
  2. changed the title [-]Timeout in user defined handler should cause retry[/-] [+]Timeout in user defined handler should cause retry (async blocking code)[/+] on Jan 15, 2025
  3. changed the title [-]Timeout in user defined handler should cause retry (async blocking code)[/-] [+]Timeout in user defined handler should cause retry[/+] on Jan 15, 2025
  4. added a commit that references this issue on Jan 17, 2025
    f4090ef
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions