You try it
Create or modify an existing HTTP trigger to start a new Orchestration instance. Have your new Orchestrator await at least two Activities (they can be the same one) so you can debug and step through to watch it rebuild its internal state. The Activity can be something minimal for this, a single API call to anywhere or something else. After it completes, view the Table Storage durable logs in Azure or Azure Storage Explorer. Examine how the logs in the history table line up with your orchestrator.