Skip to main content
Weave has the following limitations, known issues, and expected behaviors. Use this list 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
  • Object names, tags, and aliases have length and character rules, and the Python SDK rewrites object names that break them. Op names and Call display names have length limits. For details, see Naming rules and Name length limits.
  • 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:
Last modified on November 20, 2026