Common Causes of Req Delays

This article contains information on req delivery timing and lists the most common causes of req delays.

Req Delivery Timing

Average req delivery time is 30 seconds or less. As soon as there is notification of a new job, an update, or a job closure, that information is retrieved from the VMS and rapidly loaded into the ATS.

Common causes of req delivery delays include:

• Expired Credential password: Unable to log into VMS to access req details.
• Incorrect Credential Configuration: Incorrect credential configuration prevents VMS log in to access req details. This is most common with new credentials.
• VMS emails not sent to VMS Sync Credential email address: The credential email is not listed in VMS, or the email address has a forwarding rule.
• VMS emails sent to the wrong VMS Sync Credential email address: The incorrect Credential email address is listed in VMS, or the email address has a forwarding rule.
• VMS website outage: Unable to log in to VMS to access req details.
• VMS website changes: Includes Terms of Service prompts and UI changes. This requires a Support ticket to resolve.
• Req not present in the VMS: May receive the error message, "Req has been removed; should be closed". Check that the Req was not deleted form the VMS.
• ATS Save Fail: Invalid Company/Contact/Owner preventing the job from being added/updated in the ATS. Sometimes paired with an "operation timed out" error. This means VMS Sync did not receive the expected API response from Bullhorn — it does not confirm the job was never created.
• Incorrect ATS API password: Less common, as the VMS Sync API user is for VMS Sync use only, and password shouldn't be changed by clients.
• Flex Unmapped: Required to complete delivery.

For API-based position sync, VMS Sync authenticates via Client ID and Secret. Any sync issues would not be caused by inactive portal user accounts. Refer to the common delays above to troubleshoot.