Scheduling
Scheduling is available when MFT needs to pull from an external endpoint or push to an external endpoint.
You can define a file pickup or drop-off at a particular time from the Schedule tab.
-
Continuously - Allows an endpoint to automatically repeat every x Minutes, x Hours, or x Days.
-
Daily - Allows you to choose the days of the week, along with a specific time, to automate this endpoint.
-
Weekly - Allows you to set the day of the week, along with a specific time to automate this endpoint.
-
Monthly - Allows you to set the day of the month, along with a specific time to automate this endpoint.
In addition, Target Flow Endpoints have an On Arrival option. On Arrival schedules will deliver files immediately after they arrive from a source endpoint.
The On Arrival schedules activate only upon the arrival of a new file. If no additional file is placed in the designated target folder path, the "on arrival" schedule remains inactive.
However, if the target becomes available by the time the next file arrives and triggers the "on arrival" schedule, the original file will also be transferred.
If you want to schedule a flow to be triggered only by an API call, refer to Publishing a flow with no schedule (API trigger only).
Publishing a Flow with No Schedule (API Trigger Only)
To ensure a flow can only be triggered by an API call, you need to publish it without a valid schedule.
This puts the flow in a "published" and ready state, waiting for an external trigger rather than running on a timer.
The objective is to make a flow active and runnable through the API, but prevent it from ever running on its own internal schedule.
Configuring an empty schedule
-
Within the Flow Endpoint Editor, go to the Schedule tab for the flow you wish to configure.
-
Under Schedule Type, select Daily.
-
In the Days selection that appears, do not select any days of the week. Ensure all checkboxes from Monday to Sunday are not selected.
-
Click Save & Publish.
Result
Your flow is now published and active, but it has no scheduled run times. It will remain inactive until it receives a trigger from the /api/Flow/runFlowEndpointNow API call.
