argoproj/argo-workflows · error

failed to get sync limit: %w

Error message

failed to get sync limit: %w

What it means

GetSyncLimitCommand wraps any error returned by the GetSyncLimit gRPC call. It fires when reading a sync limit fails — typically because the key does not exist in the configmap/database, the --type does not match where the limit is stored, or the caller lacks RBAC permission — with the server-side cause preserved via %w.

Source

Thrown at cmd/argo/commands/sync/get.go:71

	ctx, apiClient, err := client.NewAPIClient(ctx)
	if err != nil {
		return err
	}
	serviceClient, err := apiClient.NewSyncServiceClient(ctx)
	if err != nil {
		return err
	}

	req := &syncpkg.GetSyncLimitRequest{
		CmName:    cliGetOpts.cmName,
		Namespace: client.Namespace(ctx),
		Key:       key,
		Type:      syncpkg.SyncConfigType(syncpkg.SyncConfigType_value[cliGetOpts.syncType]),
	}

	resp, err := serviceClient.GetSyncLimit(ctx, req)
	if err != nil {
		return fmt.Errorf("failed to get sync limit: %w", err)
	}

	printSyncLimit(resp.Key, resp.CmName, resp.Namespace, resp.Limit, resp.Type)
	return nil
}

View on GitHub (pinned to 35bff19146)

Solutions

1. Confirm the key, type, and configmap name
2. List existing limits to see what is configured

When it happens

Trigger: Thrown at cmd/argo/commands/sync/get.go:71 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of argoproj/argo-workflows@35bff19146 (2026-09-03). Data as JSON: /api/errors/f05f248268971bd1. Report an issue: GitHub.