Skip to main content
This page lists Weave’s limitations, known issues, and expected behaviors. Use it as a reference when you encounter unexpected results or want to understand how Weave handles edge cases.
  • For retryable requests, Weave retries requests starting at 1 second after receiving the first error and then doubles the amount of time between attempts up to 5 minutes. Requests time out after 36 hours.
  • Instead of raising exceptions, .call() captures exceptions and stores them in the call.exception. If you need to raise exceptions during execution, set the __should_raise parameter, like this:
    showLineNumbers
  • Dedicated Weave instances use a different OpenTelemetry ingress URL. For more information about authoritative endpoints, see Send OpenTelemetry traces.
  • Weave sometimes truncates large trace data objects. This occurs because the default trace output is a raw, custom Python object that Weave can’t serialize automatically. To return all of your trace data, define a dictionary of strings, like this: