Save API Workflow with a primitive connected to a forceInput pin doesn't save the primitive's value; it should

[doctorpangloss]

Expected Behavior

Connecting a primitive to a forceInput input pin saves a workflow with Save API Workflow correctly and loads that workflow with the primitive value correctly.

Actual Behavior

Connecting a primitive to a forceInput input pin, then clicking Save API Workflow, will save a workflow that has the primitive value. Loading it, however, shows the primitive value is missing. this is unexpected.

Steps to Reproduce

1. There are no vanilla forceInput nodes, so you'll have to author one.
2. Connect a primitive to the forceInput input.
3. Click "Save API Workflow" in the menu.
4. Load the workflow
5. Observe the value is missing

Debug Logs

(no notable output)

Other

No response

[geroldmeisinger]

Primitive node is always removed with Export API btw (doesn't matter were it is connected)
also see #3464 #2295

[geroldmeisinger]

This is also an issue for me. I want to use workflows via API endpoint and connect the primitive node to set multiple inputs (like steps value in 2 KSamplers).

1. If I use a primitive node it gets removed (or I set ALL nodes manually, which I want to avoid)
2. If I export with non-API I cannot change the values dynamically in JSON due to this issue widgets_values order relies on JSON Object keys order. #3547
3. If I use custom-nodes (INT Constant, Simple Int etc.) I loose the ability to set "control after generate"