When the user creates a Source Subscription Job through the Network API, it returns the success response. A Job ID is not returned. The user cannot find a Job that is created using the UI.
No changeset is available to process.
This is the expected behavior when the response is SUCCESS with no Job ID.
The Admin user can check if there is a changeset file that exists in the FTP inbound directory and there is data to update.
Network API Reference: Managing subscriptions