Frankjavir

The information you censured is accurate and supported.

Try the Citizenship Timelines in this website for your CIS, it will give you a "panoramic" view of their efficiency depending on how many Visajourney members with timelines are registered, you do not have one, so I cannot give you an answer but I can tell you, the last 10 interviews reported in Visajourney were all for filers after February 2025. Enough have been said about processing times provided by USCIS.

Encouraging data: 17 out of the last 20 citizenship interviews scheduled for Visajourney members with timelines, all filed after January 1, 2025. Its a small sample but with a huge scheduling rate of 85%.👏

@Magi Stark is correct. A case with a scheduled interview looks like this: "data": { "display_text": "Case decision", (THIS IS THE NEXT STEP) "milestone": 72, "milestone_days_remaining": 59, "ordered_display_text": [ "Attend biometrics appointment (if necessary)", "Interview scheduled", "Case decision", "Attend oath ceremony (if approved)" ], "overall": 72, "overall_days_remaining": 59, "start_date": "2025-06-09", "time_until_case_decision": "2 Months", "time_until_next_milestone": "2 Months", "outside_normal_processing_time": false, "gpt_call_failed": false

Did you receive an N-652 after your interview? That form provides you some details about the interview results. Run an API USCIS report, it will show some codes or event codes relevant to your case. (See the N-400 February 2025 filers thread for further details about API results.)

Thank you @OldUser

We wonder how common or rare are 751s without interview, it happened to us also, (back in 2018), but we are kind of worried because we assumed it was an administrative mistake and just kept quiet to see what happens at the interview for citizenship.

Congratulations!!

It's reassuring to learn that FKB is not a cause for concern; I appreciate you sharing your information, as it helps us understand these code events better. I did not mean to raise any unfounded worries; the description of the code was indeed troubling, and we are all in the process of learning about these codes. Hence, I thought it would be prudent to confirm that it wasn't an unintended request from the applicant to reschedule. I never brought up cancellation letters. There are more constructive ways to express disagreement with someone's opinion.

Thank you for your recommendation, I tried to protect it but forgot to edit 2 lines. I believe is too late for that and I am not really concerned about it. There are thousands of these numbers out there and I believe there is not much you can do with that number alone, it will be useless pretty soon. Thanks any ways !!!

This link provides all kinds of data: https://www.uscis.gov/tools/reports-and-studies/immigration-and-citizenship-data

Milwaukee N-400 stats for Quarter 1-2025 show an average of 16 processed cases per day (Assuming months of 20 working days). Therefore their average waiting time is 9.8 months. Bad thing is their numbers indicate their imput of cases per month is higher than their output.

I suggest you call and ask them who requested the cancellation and emphazise you did not make such request.

Latest USCIS Naturalizatin Data report to Congress April 2025 Latest Naturalization raw data April 2025.pdf Data files posted are available in the USCIS page. https://www.uscis.gov/tools/reports-and-studies/immigration-and-citizenship-data

USCIS Naturalization Data by FO First Quarter 2025 (Oct-Nov-Dec 2024) Naturalization 1st quarter 2025.pdf

Took me 6 months from filing to Interview, here is my USCIS API report Login into your USCIS account to obtain API report. https://my.uscis.gov/secure-messaging/api/case-service/receipt_info/IOEnnnnnnnnnn "receiptNumber": "IOE1234567890", "letterId": "123456789", "generationDate": "2025-06-09T10:28:18.198Z",06/09/25 06:28:18 AM EST "appointmentDateTime": "2025-07-28T11:55:00.000Z",07/28/25 7:55 AM EST "actionType": "Interview Scheduled" } ], "events": [ { "receiptNumber": "IOE9885135028", "eventId": "2e767d20-4c3c-4d05-a403-4f3cc2de0f1d", "eventCode": "FJ", Interview Scheduled "createdAt": "2025-06-09", "createdAtTimestamp": "2025-06-09T10:28:18.183Z", "updatedAt": "2025-06-09", "updatedAtTimestamp": "2025-06-09T10:28:18.183Z", "eventDateTime": "2025-06-09", "eventTimestamp": "2025-06-09T10:28:17.954Z" }, { "receiptNumber": "IOE9885135028", "eventId": "399f8ddd-8862-4967-a809-721e6138386c", "eventCode": "FTA0", This event basically means you qualify to apply. "createdAt": "2025-01-18", "createdAtTimestamp": "2025-01-18T01:05:16.831Z", "updatedAt": "2025-01-18", "updatedAtTimestamp": "2025-01-18T01:05:16.831Z", "eventDateTime": "2025-01-18", "eventTimestamp": "2025-01-18T01:05:16.617Z"

Flip Flop, they went back to old myProgress TAB.

That's a bummer, perhaps you will find more information about why they canceled it by looking at your API results paying attention at the codes in front of the"eventCode" lines. Login into your USCIS account and in a different screen type https://my.uscis.gov/account/case-service/api/cases/IOEyour case # The CODE descriptions are here: https://niem.github.io/model/4.2/scr/BenefitDocumentStatusCategoryCodeSimpleType/index.html

3% cases closed like yours does not make any sense, I filed 18 days after you and my info says 34%.

USCIS case status timeline changed its format for the worst, no info on NOA, Biometrics, Interview, just plain time information that any one knows by looking at a calendar,

Congratulations!!, When did you apply?

FJ is an event code meaning your interview has been scheduled. Login and query your case with https://my.uscis.gov/account/case-service/api/cases/IOEnnnnnnnnnn. I queried my case with your CLI and obtained my receipt number and CIS office: { "data": { "receipt_details": { "form": "N-400", "location": "OKL", [THIS IS OAKLAND PARK FL] "milnatz": 0, "onpt": 0, "premproc": 0, "receipt_date": "Sat, 18 Jan 2025 00:00:00 GMT", "receipt_number": "IOEnnnnnnnnnn", "subtype": "160A" Any one can throw some light on the meaning of the other lines, like subtype 160A, etc?

Did you get an update with a FJ code?

Does any one know how to decode the IOE number? It cannot be first 2 digits the fiscal year, next 3 the day, and they do not seem to be progressive because higher numbers were already processsed few years ago. I found a website that provides lots of API data, I apologized for posting it, I did not remember certain rules about posting. My IOE is way lower than the list below.

"data": { "receiptNumber": "IOExxxxxxxxxx", "submissionDate": "2025-01-18", "submissionTimestamp": "2025-01-18T00:00:00.000Z", "formType": "N-400", "formName": "Application for Naturalization", "updatedAt": "2025-03-14", UPLOADED AN UPDATED FORM WITH NEW VERSION "updatedAtTimestamp": "2025-03-14T01:36:16.278Z", "cmsFailure": false, "closed": false, "ackedByAdjudicatorAndCms": true, "applicantName": "Last name, First name", "noticeMailingPrefIndicator": false, "docMailingPrefIndicator": false, "elisBeneficiaryAddendum": { }, "areAllGroupStatusesComplete": false, "areAllGroupMembersAuthorizedForTravel": true, "isPremiumProcessed": false, "actionRequired": false, "elisChannelType": "EFile", "concurrentCases": [], "documents": [], "evidenceRequests": [], "notices": [], "events": [ { "receiptNumber": "IOExxxxxxxxxxxxx", "eventId": "399f8ddd-8862-4967-a809-721e6138386c", "eventCode": "FTA0", "createdAt": "2025-01-18", "createdAtTimestamp": "2025-01-18T01:05:16.831Z", "updatedAt": "2025-01-18", "updatedAtTimestamp": "2025-01-18T01:05:16.831Z", "eventDateTime": "2025-01-18", "eventTimestamp": "2025-01-18T01:05:16.617Z" }, { "receiptNumber": "IOExxxxxxxxxxxxxx", "eventId": "b0b399db-ce47-4c05-a6a6-7fef3ae4d108", "eventCode": "FTA0", "createdAt": "2025-01-18", "createdAtTimestamp": "2025-01-18T01:05:16.816Z", "updatedAt": "2025-01-18", "updatedAtTimestamp": "2025-01-18T01:05:16.816Z", "eventDateTime": "2025-01-18", "eventTimestamp": "2025-01-18T01:05:16.621Z" }, { "receiptNumber": "IOExxxxxxxxxxxxxxx", "eventId": "e8bf03b9-902d-4730-a9c2-f4afca89518f", "eventCode": "FTA0", "createdAt": "2025-01-18", "createdAtTimestamp": "2025-01-18T01:05:16.679Z", "updatedAt": "2025-01-18", "updatedAtTimestamp": "2025-01-18T01:05:16.679Z",