This is what North Shore refers to as a composite workflow. Which to us denotes that it’s made of component parts.
Your ingest is a part, that’s already done. Then you can add other pieces to the workflow and either call them separately, by different metadata flags, or all at once by making versions that trigger the next.
In this case I’m assuming you have a proxy status field that will trigger the creation of proxy.
You could simply add another “analyze” step as a worker node action and trigger them separately, or set the analyze to trigger the pros creation after it runs which would give you a composite workflow which would allow you to trigger both, for assets that needed it. Or just trigger proxy on its own.
Sounds like this would be a fast call to your integrator or you could play around in the worker and probably figure it out, depending on your time available.
This “Analyze Later” has become a stock workflow for North Shore in the last few months due to the high volume of people who have bulk ingest jobs this year where they need to quickly ingest tens of thousands of assets.
One caveat, we tend to only pull one to three thumbnails when ingesting large sets. This makes it faster and keeps the db size down. You can always go back and pull more thumbs later with the desktop client.