Fergus Booking Forms

Fix a Fergus booking that did not reach Fergus

7 min read Fergus booking form

Start on the Bookings page. A booking that did not reach Fergus carries a red status, and the Dashboard counts them under "Needs attention" for the last 30 days: "A booking from the last 30 days has not reached Fergus. Open it to send it again." Open the booking. The reason is in the red box at the top and, with the call and the data sent, under Integration Errors.

Sending a booking again carries on from the step it stopped at. Whatever was already made in Fergus is kept, and nothing is made twice. Where this article says to send it again, that is the Send again button.

Status by status

Waiting

The booking was saved in the last two minutes and has not been picked up. Reload in a moment. It cannot be sent again yet.

Not sent

There are two causes.

  • A reason is shown. The booking was picked up and failed. Read the reason (the common ones are below), fix the cause, then send it again.
  • "This booking was never picked up". Nothing started work on it within two minutes. Send it again.

Sending and Stopped

Sending is a run in progress. A run still going after ten minutes has died, and the status becomes Stopped. Send it again. Sending is refused while a live run still holds the booking.

Blocked

The customer matches your block list, so nothing was made in Fergus and no booking email went to your office. The booking page names the match. If the customer should not have been blocked, take them off the block list and ask them to book again. A blocked booking cannot be sent again.

Sent, files not sent, Sent, files stopped and Sent, files not received

The job and visit are in Fergus. A file failed, stalled, or never arrived. Send again sends only the files. If the customer's browser never uploaded a file, Formpiece has nothing to send, and you need the file from the customer.

Sent, office not emailed

The booking is in Fergus and the email to your office did not go. Send again sends only the email. If it fails again, the reason is under Integration Errors, headed "Notification email". Check the addresses on Notification recipients. A form on the Free plan has no recipients, so nobody is emailed about a failed booking either. Watch the Bookings page instead.

Reasons you may see

  • "The Fergus login has lapsed and has to be signed in to again.", "The Fergus credential for bookings could not be found. Reconnect Fergus in the dashboard." or "No Fergus credential has been chosen for bookings." The credential is the problem. See Credentials expired below.
  • "The time the customer picked has already passed, so the visit was not added to Fergus. Arrange a new time with the customer." The booking was sent again after its time began, so the visit was not added and the booking stays Not sent. Arrange a new time with the customer and book the visit in Fergus.
  • "Fergus did not answer ... in time. It may or may not have been done, so send the booking again and it will be checked for first." Send it again. Formpiece looks in Fergus for the record before making another.
  • "The function ran out of time before ... Send the booking again to carry on from where it stopped." Send it again.
  • Fergus's own words, beginning "Fergus responded" followed by a status. Fergus refused something it was sent. Read what it names, correct it in Fergus or on the form, and send the booking again.
  • "Fergus said the customer already exists but did not say which one. Find it in Fergus and send the booking again." Merge or fix the duplicate in Fergus first.
  • "The visit was removed or is a repeating event, so it could not be moved." and "The visit is shared by several people in Fergus, so it could not be moved online." These are auth link bookings that move a visit. Move it in Fergus.
  • "This booking made too many requests to Fergus and was stopped." A safety limit. Sending it again starts a new count.
  • "The booking could not be completed because of a problem on our side. Send it again ..." A fault on Formpiece's side, with no detail shown. Send it again once. If the same message comes back, there is nothing to change in your settings.

The customer saw "That time is no longer available. Please choose another."

The form checks the time again at the moment the customer sends it, against the live Fergus calendar and the form's own rules, including regions and Geosearch. If someone has taken the time or the staff member has since become busy, the customer is told to pick another. Nothing is saved, so the booking does not appear in the list. Search Diagnostics shows what the form offers a given address now.

Double booking protection

The calendar is read from Fergus and kept for about ten seconds. A booking is not in the Fergus calendar until it has been made there, so for its first 30 minutes the booking itself holds the time for that staff member and their team, from the start of any drive before the visit to the end of any drive after it. When two customers send the same time together, only one claim on the time succeeds and the other gets the message above.

A booking that has failed stops holding its time at once, and one still waiting or sending lets go after 30 minutes. The time can then be offered to the next customer. Check the staff member's Fergus calendar before sending a booking again after a gap.

Free plan limits

A form on the Free plan keeps every setting you made but applies fewer. At booking time it uses the first service only, and ignores time groups, callbacks, team members, categories, regions, Geosearch, customer and site lookups, attachments, questions, scripts, notification recipients and email wording, working days, public holidays, redirects and tracking. A quote books as an estimate. Plans and features has the full list.

The booking API applies these limits live when customers use the form. A form saved on Business that then lapses to Free behaves as a Free form straight away, and its settings return when the account moves back to Business.

A form needs publishing again

Customers are served the published copy of the form, which is written when you save. If the copy is behind, customers see the older form. Signs of it:

  • A save ends with "The form was saved but could not be published to the ... database. Use Publish again on the form to try again." The settings are saved, and the published copy is not.
  • The forms list reports "Could not publish ... again. Use Publish again on the form."
  • Check on an auth link fails Form is published.
  • Search Diagnostics does not show a change you just saved.

Open the form and click Publish again at the top, or use it from the menu on the forms list. Changing a region updates the forms that use it, and if that publish failed, Publish again finishes it. An archived form stops serving customers.

If a save says "This form was saved somewhere else after you opened this page. Reload the page to pick up those changes before saving again.", someone else saved it first. Reload before changing anything.

Credentials expired

The Fergus connection can fail in three ways, and the Fergus bookings Dashboard shows each.

  • "The Fergus connection was revoked or has lapsed, so bookings cannot be sent to Fergus. Connect Fergus again to carry on." with a Reconnect Fergus button. The connection badge reads "Needs connecting again".
  • "The Fergus access token expires in 12 days." A Personal Access Token lasts a year and nothing renews it. The dashboard shows this warning from 30 days ahead.
  • "The Fergus access token has expired, so nothing can be sent to Fergus until it is replaced." The badge reads "Token expired".

Replace or reconnect the credential, as Fergus credentials describes. Bookings customers made while it was down are Not sent. Open each one and send it again.