Issue Summary

If Insight get's inundated with requests from automation whilst simultaneously running an import the automation rules can fail to get the information back in time and thus fail.

Steps to Reproduce

1. Set up an automation rule that is triggered by objects that are created/updated or deleted from a specific schema. Add in some object based components to this rule that will call back to insight. Like lookup objects or create object or edit object.
2. Set up an Import inside of insight into the same schema the rule is triggered on. Make sure to import a sufficient amount of objects. Author tried with 5000.

Expected Results

Insight can handle this load and the rules wont fail despite being run at the same time that the import is running.

Actual Results

The below exception is thrown in the xxxxxxx.log file:

{ [-]
   @tag: kube
   caller: sidecar/sidecar.go:281
   computationgroup_id: 123xyz    customer: shared
   env: prod
   error: context canceled
   host_type: k8s
   hostname: ip-10-16-0-115.ec2.internal
   k: { [+]
   }
   level: error
   message: backend service failed to respond
   region: us-east-1
   request_agent: Automation for Jira AC app/1.0
   request_host: 123xyz.internal.shared-prod.us-east-1.kitt-inf.net
   request_id: 70a59a341d382bfa
   request_method: GET
   request_proto: HTTP/1.1
   request_referer:
   request_remote: 10.36.6.0:46448
   request_url: /rest/insight/1.0/object/6888
   timestamp: 2021-12-16T21:19:12.822Z
   version: 2021-12-10T22:46:10.362214Z-7e4bebc4959db79d46178f5f6dfcdd595d72703a
   workspace_id: 123xyz
} 

Workaround

Turn off the rule during an import or reduce the import size potentially splitting into multiple files.