What to do if your scheduled file transfer does not run or is delayed

If we have a scheduled transfer that does not run when it is due or is delayed, it might be because the agent is processing commands on its command queue. Because the agent is busy, scheduled transfers are not checked and are therefore not run.

• Configure the maxSchedulerRunDelay property in the agent.properties file to set the maximum interval in minutes that the agent waits to check for scheduled transfers. Setting this property ensures that the agent keeps checking for scheduled transfers even when the agent is busy. For more information about the property, see The MFT agent.properties file.
• Alternatively, use a resource monitor instead of a scheduled transfer. Resource monitors work differently from scheduled transfers and are not affected by the agent being busy. For example, if we want an up-to-date file on the destination system, resource monitors reduce network traffic. This is because the file is transferred only when a new version becomes available, rather than the file being transferred automatically. However, resource monitoring is not supported on protocol bridge agents or Connect:Direct bridge agents.

  For more information, see Monitor MFT resources.

Parent topic: MFT general troubleshooting