UCAS Sync and Troubleshooting
This page explains when the UCAS integration exchanges data with UCAS, how imported applicants appear in Full Fabric, how to read the sync status, and what to do when something goes wrong. Setup, course matching and decision mappings are covered on the UCAS page.
What Syncs and When
Applicant data flows from UCAS into Full Fabric. Only decisions (and the automatic password change) are written back to UCAS. Each scheme syncs on its own.
| What | When | Direction |
|---|---|---|
| Applicant sync | Twice a day, at 06:00 and 18:00 (Full Fabric server time), for every enabled scheme whose credentials UCAS accepts | UCAS → Full Fabric |
| Sync Now | On demand, from the scheme card | UCAS → Full Fabric |
| First sync | Right after a scheme is enabled, once reference data is refreshed | UCAS → Full Fabric |
| Follow-up sync | After Full Fabric sets up a new cycle | UCAS → Full Fabric |
| Reference data | Daily at 05:00: UCAS code lists used to turn codes into readable descriptions | UCAS → Full Fabric |
| Password check | Daily at 04:00: refreshes Password expiry and changes the password when 14 days or fewer remain | Both |
| Decisions | Shortly after a journey moves to a mapped state | Full Fabric → UCAS |
Each applicant sync fetches the applicants whose UCAS record changed since the scheme's last successful sync (the very first sync fetches them all). A sync that fails does not move that point forward, so the next one fetches the same changes again. Only one sync runs per scheme at a time; a sync that hits UCAS rate limits is retried automatically.
How UCAS Applicants Appear
Profiles. Full Fabric first looks for the profile it created or matched for that UCAS application before, then for a profile with the applicant's email address, and creates a new profile only when neither exists. Later syncs refresh the first and last name from UCAS; the email is only filled in when the profile has none.
Applications. Each applicant gets one application per scheme and cycle, on that cycle's UCAS Applications template. The application is submitted on the applicant's behalf once at least one of their choices is mapped to a programme (see Course Matching). After that, each sync updates the application's documents and maps them to the profile again, without resubmitting it.
| Document | Scheme | Contents |
|---|---|---|
| Personal Details | Both | Names, contact details, addresses, date of birth, nationality, residency and visa, UCAS Personal ID, Application Scheme Code, Special Needs |
| Qualifications | Both | Declared qualifications and exam results |
| Personal Statement | Both | The applicant's statement |
| Reference | Both | Referee details and reference text (Conservatoires: academic and practical referees) |
| Education | Both | Education history |
| Choices | Both | Programme (the matched classes) and Course Choices: every UCAS choice with its course, campus, UCAS decision, applicant reply, offer conditions and start date |
| Additional Information | Both | Widening participation and background answers, last school, disability; Undergraduate also higher education activities and parental higher education |
| Audition | Conservatoires | Audition details for each choice |
| Instruments | Conservatoires | Study areas and instruments for each choice |
| Fees | Conservatoires | Application fee, course fees and payments |
Note: For recent cycles UCAS sends disability information separately from the applicant's details. Full Fabric writes the condition to Disability/Mental Health under Additional Information and the applicant's free-text details to Special Needs; the Disability field in Personal Details stays empty.
UCAS templates have applicant notifications switched off, so the Notify applicant automation action skips UCAS applications.
Sync Status
The Sync Status section of an enabled scheme card shows the latest sync's status, Last sync, Errors (last 7 days) (the number of syncs in the last seven days that ended partial or failure), the Sync Now button and the five most recent syncs:
| Column | Values |
|---|---|
| Status | success, partial (some applicants could not be processed) or failure (the sync stopped) |
| Type | automatic (scheduled or follow-up), manual (Sync Now) or initial (after enabling) |
| Processed | Applicants imported or updated |
| Errors | Click (view) to open Sync errors, listing each UCAS Personal ID with its Error |
While a sync is running or queued, Sync Now is unavailable and the status shows running; the page refreshes until the sync finishes.
Common Problems
UCAS rejected the stored credentials
When UCAS rejects the scheme's saved username or password (during a sync, the daily password check or a decision), Full Fabric disables the scheme so further attempts cannot lock the account. The scheme card shows UCAS rejected the stored credentials with the time it was detected and UCAS's response, a sync that was running shows failure, and the staff member who enabled the scheme receives an email saying so. Scheduled syncs stop until it is fixed.
Fix: click Update credentials, enter the current values, click Validate and save credentials, then Enable. If the saved values are still correct, Validate credentials checks them again without retyping.
UCAS account locked
Validation shows UCAS account locked. This UCAS account is locked after repeated failed login attempts. Contact UCAS to unlock it before trying again. UCAS locks an account after three failed sign-ins. Ask UCAS to unlock it, then validate once with the correct password.
UCAS service unavailable
Validation shows UCAS service unavailable. Please try again later. when UCAS returns an error other than a rejected sign-in. Nothing is saved; try again later. Any other validation message is UCAS's own reason for rejecting the credentials.
A new cycle has started
The first sync that sees applications for the next cycle ends partial, with errors such as No ug template for cycle year 2027; application dropped. Cycle setup is queued; a follow-up sync will pick it up. This is expected once per cycle. Full Fabric creates the new template, refreshes reference data, carries course mappings forward and runs a follow-up sync that imports those applications; Sync Now stays unavailable meanwhile. Afterwards, check the new cycle's Course Matching table. If an error instead ends with Run a full sync after creating the template to pick it up, this sync did not set up that cycle; if the error keeps appearing in later syncs, contact Full Fabric support.
Applications are not submitted
The application stays unsubmitted while none of its choices is mapped. In Course Matching, the course shows as unmatched: map it and keep Update N existing application(s) with this mapping checked.
Applicant errors on a partial sync
Each row in Sync errors is an applicant Full Fabric could not process; the other applicants were imported. The sync still counts as completed, so a listed applicant is fetched again only when UCAS next updates their record.
A decision did not reach UCAS
Decision failures are not listed on the settings page. A decision is not sent when:
- The new journey state is not mapped, or the same decision was already sent for the choice
- U or GU was sent and the new state maps to REJ
- The journey is not in the class the choice was matched to, the application is not in a live cycle, or the scheme is disabled
- The UCAS choice lacks a course code or start date (Conservatoires also need a study mode and first instrument)
If UCAS rejects the decision, nothing is recorded as sent. Move the journey to an unmapped state and back to the mapped one to send it again.