Greengrass V2: ComponentDependencies - Soft vs Hard

Currently running Greengrass v2 nucleus 2.8.1

In the following setup, I notice that with the following dependency chain Component 3 runs after Component 1 and 2 have been installed, but Component 1 is still in the starting state. C3 needs the service in C1 fully started in order to start itself, which in turn causes component 3 to enter a failed state. Should I make C3 hard depend on C1? What is the right way to set up the dependency chain?

[Component 1] --Hard Depend--> [Component 2] --Soft Depend--> [Component 3]

An incomplete yaml:

---
# Component 3
componentType: "GENERIC"
dependencies:
- "component2:SOFT"
lifecycle:
  Run:
    Script: "service.exe"
---
# Component 2
componentType: "GENERIC"
dependencies:
- "component1:HARD"
lifecycle:
  Startup:
    Script: "something.exe"
---
# Component 1
componentType: "GENERIC"
lifecycle:
  Install:
    Script: "install.exe"
  Startup:
    Script: "something-that-takes-long-to-start.exe"