General troubleshooting

If you encounter general issues while configuring or using Automation Suite, see the following:

Failure to publish packages from Studio

Description

In certain situations, some API calls to Automation Suite can result in a 413 response (or RequestEntityTooLarge error message). The conditions can occur when:

The request is over 1MB in size.
The HTTP version used is 1.1.

The issues is encoutered in common scenarios like publishing a package from Studio, uploading queueItems, or any other scenario where Activities or Studio are posting files or data to Orchestrator.

Solution

To avoid this issue, you can increase the default buffer limit to a larger value, such as 10MB. To do this, you can change the Envoy Filter settings to adjust per_connection_buffer_limit_bytes to a larger byte value.

The following example shows how to set per_connection_buffer_limit_bytes to 10000000 bytes:

cat > /tmp/increase_buffer_per_connection.yaml <<'EOF'
kind: EnvoyFilter
metadata:
  name: increase-per-conn-buffer-envoy-filter
  namespace: istio-system
spec:
  configPatches:
  - applyTo: LISTENER
    patch:
      operation: MERGE
      value:
        per_connection_buffer_limit_bytes: 10000000 #10MB
EOF
kubectl apply -f /tmp/increase_buffer_per_connection.yamlcat > /tmp/increase_buffer_per_connection.yaml <<'EOF'
kind: EnvoyFilter
metadata:
  name: increase-per-conn-buffer-envoy-filter
  namespace: istio-system
spec:
  configPatches:
  - applyTo: LISTENER
    patch:
      operation: MERGE
      value:
        per_connection_buffer_limit_bytes: 10000000 #10MB
EOF
kubectl apply -f /tmp/increase_buffer_per_connection.yaml

On this page

Failure to publish packages from Studio
Description
Solution

Was this page helpful?

PREVIOUSRke2-coredns-rke2-coredns-autoscaler pod in CrashLoopBackOff

NEXTFailure to get the sandbox image