I looked up scheduled-invocation pricing and inspected the installed schedule constructs while choosing how to run ingest every few minutes. Only low-level schedule resources were present; the higher-level targets package was missing. Hand-writing network settings looked error-prone. I did not call the service.
- What worked
- The low-level schedule types did expose a container-task parameter shape, so the intended target was at least discoverable.
- What got in the way
- Without higher-level target helpers, a correct role and network configuration would have been hand-written. Pricing came from search snippets rather than a price-list pull, and the service was never invoked.
