Home/Blog/Ashby Recruiting Blocks: Fix Missing Availability
Recruiting operations guide

Ashby Recruiting Blocks: how to fix missing interview availability

Set up Ashby Recruiting Blocks with the right calendar, titles and schedule suffixes. Diagnose missing slots before changing interviewer availability.

Remqa · November 22, 2026 · 5 min read

Short answer

To fix missing availability in Ashby Recruiting Blocks, check the primary connected calendar, event title visibility, exact title and any schedule-specific suffix. Then check dates, declined invitations, interview duration and the selected conflict setting. A custom schedule suffix takes precedence over personal blocks, so open calendar time alone may not create a bookable slot.

  • Blocks must be on the primary connected calendar with readable event titles
  • A custom schedule suffix uses its own matching events instead of personal blocks
  • Allowing ordinary meeting conflicts does not allow overlapping Ashby interviews
  • Retest active booking links after changing the schedule configuration

A candidate opens an Ashby booking link and sees no times. The interviewer has space on the calendar, so the coordinator asks them to create more availability. Before adding anything, check which Recruiting Block the schedule actually expects. An event on the wrong calendar, a hidden title or a different suffix can make real interview capacity invisible to that booking link.

This guide focuses on that configuration problem. It separates Ashby's native availability rules from a proposed AI diagnostic workflow. An agent can prepare a useful exception brief. The recruiter should still decide which calendar event or schedule setting needs to change.

Start with the calendar Ashby can read

Recruiting Blocks are calendar events. They must sit on the interviewer's primary connected calendar. Ashby does not detect events on secondary calendars as Recruiting Blocks, even when those calendars otherwise contribute conflicts or availability. A shared planning calendar with the right event name is therefore not enough.

Ashby must also be able to read the event title and time. If integration permissions expose only busy time, the application cannot identify the event as a Recruiting Block. Check visibility through the connected calendar integration before changing the interview schedule. Avoid copying unrelated meeting details into a troubleshooting ticket.

Copy the title shown in Ashby rather than typing an approximation. Capitalization does not matter, but spelling, spaces and punctuation do. Personal block titles cannot be customized. The event can be marked Free or Busy because recognition depends on its title, not its native free/busy status.

Choose personal blocks or dedicated schedule capacity

Personal Recruiting Blocks describe when one interviewer should be available across interview schedules. Schedule-level blocks reserve capacity for a particular schedule interview activity. Use that distinction to answer a concrete operating question: should this time be usable across interviews, or held for this specific workflow?

ConfigurationEvents Ashby checksWhat to verify
Personal blocks onlyThe standard personal block titleThe matching event exists on the target date
Schedule blocks without a suffixThe standard Recruiting Block titleOrdinary unsuffixed block events are present
Personal and unsuffixed schedule blocksThe same standard block titleThe shared capacity is intentional
Schedule blocks with a custom suffixOnly the corresponding suffixed titleThe personal block is not being counted as dedicated capacity

A custom schedule suffix takes precedence over personal blocks for that schedule. If the schedule expects Ashby Recruiting Block [engineering], an event titled Ashby Recruiting Block does not make the interviewer available for it. General open calendar time and meeting hours do not create the missing dedicated block.

Check the expected title before asking for more time. A calendar can contain a valid personal block and still provide no availability for a schedule that requires a custom suffix.

Set up the workflow in dependency order

  1. Confirm that the feature is available in the organization's current setup and that personal blocks are enabled where needed.
  2. For personal availability, open Personal settings, then Meeting Hours & Recruiting Blocks. Turn on the setting and copy the displayed title.
  3. For dedicated capacity, open the job's Interview Plan and edit the relevant schedule interview activity. Open Meeting Hours and enable Recruiting Blocks.
  4. Decide whether the schedule should use the standard title or a custom Schedule-specific suffix. The suffix field accepts lowercase letters, numbers and hyphens.
  5. Create the corresponding events on each eligible interviewer's primary connected calendar. Confirm title visibility and the intended dates.
  6. Choose how ordinary overlapping calendar meetings affect the block, then test the candidate-facing availability.

Shared events can be used to invite interviewers to the reserved time. An invitation does not need to be accepted for Ashby to recognize the block. A declined invitation is different: Ashby ignores that block for the interviewer. Keep that distinction in the coordinator's checks.

Decide which conflicts remain protected

The conflict setting has a direct operational consequence. Allow scheduling over non-interview meetings treats the block as available despite ordinary meetings that overlap it. Don't schedule over existing meetings makes the overlapping portion unavailable. Choose the rule with the interviewer rather than assuming every meeting is movable.

Ashby-managed interviews remain conflicts under either choice. Allowing non-interview conflicts does not permit two Ashby interviews to overlap for the same interviewer. If an AI assistant drafts an explanation for a missing slot, it should identify the type of conflict instead of recommending that the coordinator ignore every busy event.

Auto-scheduling considers matching block events. Meeting Hours can influence recommendations, but do not prevent booking inside a valid block outside those hours. Manual scheduling is a separate exception path. The scheduler can book outside a block when needed, while direct booking and auto-scheduling continue using the configured availability.

Troubleshoot an empty booking link in this order

  1. Identify the exact schedule interview activity behind the candidate's link. Record whether a custom suffix is configured.
  2. Check the primary connected calendar for the required event title. Do not stop at a screenshot of another calendar.
  3. Confirm that Ashby can read the title and time. A visible event in the calendar application does not establish integration visibility.
  4. Check the requested date. Confirm that a recurring series has not ended and that the interviewer has not declined the event.
  5. Check the continuous window against the interview duration. Adjacent or overlapping matching blocks combine, but the full interview must fit.
  6. Inspect overlapping events under the chosen conflict setting. Keep Ashby-managed interview conflicts separate from ordinary meetings.
  7. Retest the candidate link after correcting the configuration and allowing the calendar change to sync.

Do not treat a configuration edit as a confirmed fix. Active booking links use the schedule's current Recruiting Block configuration. Changing or removing a suffix changes the event title those links expect and can change the availability they show. Test an existing link as well as the edited schedule.

Use AI to prepare a diagnostic brief

A custom agent can help collect the checks above into one reviewed brief. This is an implementation recommendation, not a claim that Ashby includes an AI Recruiting Blocks debugger. Start with the affected schedule, expected title, connected calendar, target date and evidence for each failed check.

Keep unknowns explicit. If the agent cannot verify title visibility or the invitation response, mark that check unverified. Give the coordinator a proposed correction and a retest step. Do not let an inferred cause trigger a calendar edit, conflict-policy change or candidate message automatically. Our interview scheduling automation guide covers the broader handoff between preparation and approved action.

Common mistakes include adding blocks to a secondary calendar, renaming a personal block, ending a recurring series and changing a suffix without retesting existing links. Another is treating a successful manual exception as proof that the direct booking setup is fixed. Keep the exception and the underlying repair separate.

How Remqa can help

Remqa builds AI agents for recruiting teams around the work that needs a clear owner. For a scheduling diagnostic workflow, scope the inputs, limit calendar access, define the review step and test the candidate-facing result. Use the recruiting workflow map to place that work alongside the coordinator's other tasks. Bring one failing schedule and the intended availability to a conversation with an engineer.

FAQ

Questions people ask.

Why does an Ashby booking link show no availability?

Check that the interviewer has a matching block on the primary connected calendar and that Ashby can read its title and time. Also check the schedule suffix, event dates, declined invitations, available duration and conflict setting.

Can Ashby Recruiting Blocks use a secondary calendar?

No. Ashby does not detect Recruiting Blocks on secondary calendars. Put the matching event on the interviewer’s primary connected calendar, even if another calendar otherwise contributes conflicts or availability.

Does a schedule-specific suffix override personal blocks?

Yes. A schedule with a custom suffix looks only for its corresponding event title. An unsuffixed personal block does not supply availability for that schedule.

Can Recruiting Blocks allow overlapping interviews?

The option to allow scheduling over non-interview meetings can ignore ordinary meeting conflicts inside a block. Ashby-managed interviews remain conflicts and cannot be double-booked through that setting.

Can a recruiter manually schedule outside a Recruiting Block?

Yes. Manual scheduling can be used for an exception. Direct booking links and auto-scheduling continue to use the configured Recruiting Block availability.

Talk to an engineer

Want an engineer to look at your setup?

Book a free 30-minute call. We look at your tools and your team's week and tell you what we would do first.

Book a free 30-minute call
30 minutesFree, with an engineer
Your stackWe look at what you run today
Straight answerIncluding when we're not the fit