Does any other API Workflow scheduling cause the same behaviour?
It might be limited to your current scheduled API workflow only, which leads to ask yourself about what inside that specific API workflow.