Answer
This is the API intentionally refusing to create a record that a subsequent read operation would immediately filter back out — it can be caused by values in your payload, or by a WHERE-style condition built into the underlying datasource, that would make the just-created record inaccessible to the same user/context right after creation; the API is designed to prevent creating something you then couldn't see or reach. To isolate the cause, call the same endpoint with the identical payload from a tool like Postman using the same user credentials — reproducing it outside the workflow confirms whether it's a genuine data/access issue rather than something specific to the workflow engine itself.