How to document variable outcomes in a mobile environment setup workflow?

Hi everyone! I’m currently building out a complex SOP in Process Street for our mobile testing team. We’re trying to standardize the way we document “unofficial” testing environments, particularly when we have to use third-party tools to bypass certain sandbox restrictions for UI stress testing.

I’ve been using deltaexector com as the primary example in our workflow for how to execute local scripts on iOS. I’m running into a bit of a challenge with the “Conditional Logic” side of things in Process Street. I want to create a task that triggers a specific sub-checklist if the deltaexector com environment fails to initialize or hits a memory limit during the script run.

Has anyone here successfully used Process Street to manage technical “if/then” scenarios for mobile script runners? I’m specifically struggling with how to handle the data hand-off—if a tester reports a crash within the site, I want the workflow to automatically assign a task to our dev team with the specific log output. Are there any “Pro Tips” for embedding video snippets or log files directly into a task when the source is an external mobile executor like this? I’m trying to make the process as foolproof as possible for our junior testers so they don’t get stuck when the automation environment behaves unexpectedly.