No. It focuses primarily on reliable object-processing operations performed in Object Mode. Actions that depend on Edit Mode, Sculpt Mode, node editors, animation editors, or other interactive contexts may not be recorded. The recording report identifies actions as Captured, Partially Captured, or Not Recorded.

You can choose from three failure-handling modes: Restore That Object restores the failed object and continues. Restore Entire Batch stops the run and restores all targets. Keep Partial Changes preserves changes made before the failure.

Shared .sfrflow files contain serialized workflow data, not Python source code. Imported workflows cannot execute Python, delete objects, or open and save .blend files. Imported workflows also display a permission summary before their first run. However, users should still inspect all steps and test unfamiliar workflows on duplicate objects.

es. An Export FBX step can generate files for multiple targets. Dynamic placeholders such as {object_name}, {index}, and {workflow_name} can be used to create unique filenames and paths. Example: //exports/{object_name}.fbx

Yes. You can add steps manually or begin with one of the included Starter Actions.

Common supported modifiers include Bevel, Mirror, Array, Solidify, Subdivision Surface, Boolean, Decimate, Weld, and Weighted Normal.

A step may be skipped because: It is disabled Its conditions did not match The target object is incompatible The required selection count was not met A conditional skip is expected behavior and is not considered a failure.