Now

The Declined tab was ordering itself by the wrong date, which made a request you had just lost very hard to find.

When a request you sent goes 14 days without an answer, cord closes it. It kept the date of your original message though, so it dropped into the Declined tab as if nothing had changed and sat wherever it had always sat. One person had four expire inside two days and could not find any of them. The expiry date now drives the order, so the ones that just lapsed are at the top.

Your experience goes stale the moment you stop editing it, and most people stop editing it. cord can now keep that section current from your LinkedIn profile, and there is a switch in Settings if you would rather it did not. Two fixes to your profile page went out alongside it.

Additional Features

• Choose whether cord refreshes your profile: There is a new card in Settings called "Keep my profile up to date". If your profile has a LinkedIn URL on it, cord uses that to refresh your experience from time to time. It only adds and updates, and never removes anything you have written yourself. It starts on, and the toggle turns it off.

Fixes

• Current roles no longer flagged as a date error: A role you are still in showed a red "Incorrect date period. Please edit and fix." where its length should have been. An open end date was read as the year -1, so every ongoing role looked like it had finished before it started. Current roles now show how long you have been there, on your experience and on your projects.

• Your location shows on your profile: If your city had been saved as plain text with no matching place record behind it, your profile showed no location at all. Saving your city now matches it to a real place, so it appears where it should.

Writing a detailed job description and hitting save returned "an error occurred" with nothing to act on, so people rewrote the post, tried again, and gave up. One company tried 21 times in under a minute. Descriptions past roughly 8,000 characters of formatted text were quietly hitting a limit in how the change was published behind the scenes. Length is no longer a limit, and saving works the same whether you make the edit or cord's team does.

A position posted on a Friday afternoon had no intros until Tuesday morning. Fixing that turned up four more paths where a position quietly ended up with no intros at all, or with intros for a role that was no longer live.

Improvements

• First intros on the day you post: Creating a position saved the role and then waited for the overnight run to fill it, so a role posted on a Friday afternoon had nothing to look at until Tuesday morning, around 66 hours later. Intros are now generated as soon as the position is created. The daily refresh covers every day of the week too, where Saturday and Sunday used to be skipped.

Fixes

• Resuming a position brings its intros back: Resuming a paused position said it worked and then did nothing. The step that should have rebuilt the intros failed on a malformed query and the error was swallowed, so the role came back live with an empty Intros page. Resuming now restores them.

• Joining a hiring team gets you your own intros: Joining a position from the hiring team is the quickest way onto a role, and it was the one route that created no intros at all. Joining now generates them, and leaving clears them.

• No intros for positions you have closed: Intros stayed on positions that had been archived, paused or deleted, and messaging anyone on that list failed. Intros now show only for positions that are still live, and archiving or pausing a role clears them.

• External roles no longer generate intros: A position that sends people to another system to apply cannot be actioned on cord, so building an intro list for it spent a search and a ranking pass on people nobody could message. Those are skipped now.

• Core skills weighted in the order you ranked them: The ranking read your core skills back to front, so the skill you listed first, the one that matters most, carried the least weight and the last one carried the most. The order now counts the way you set it. The weighting no longer depends on how many skills you list either, so a position with more than five core skills ranks like the rest.

Three things that were going wrong quietly. The largest was a filter panel building itself before anyone had opened it, which is what locked up Discover on load for some users.

For everyone

• Tabs that pick up the latest version: A tab left open kept running whichever version of cord it loaded with, until you navigated out of the app entirely. One customer sat on a four-day-old build and hit a bug that had been fixed and released days before. cord now checks for a new version every 15 minutes and whenever you come back to the tab. A tab you have not touched for an hour reloads itself quietly, an active one picks the new version up the next time you move between sections, and neither will reload over a position you are part-way through writing.

For job seekers

• Newsletter and events emails you can turn off: Switching "Newsletter and events" off in your email settings said "Saved", then showed the toggle back on the moment you reloaded, and the emails kept arriving. Nothing had been written. It affected everyone verified before February 2024, because that setting only got a record at verification and older accounts never had one. Turning it off now creates the record on the spot, and the emails stop straight away rather than up to an hour later.

For companies

• Company feeds that respond straight away: Opening a company feed under Discover looked ready, then locked up for a few seconds if you clicked a filter, scrolled, or switched job role, sometimes far enough for Chrome to offer "Page Unresponsive". The filter panel was building 2,065 checkboxes and around 10,500 page elements before you had opened it, 1,726 of them the 863-item skills list rendered twice, once for Core skills and once for All skills. Each panel now builds its options when you open it, so landing on a feed with the filters closed builds none of them instead of 2,062, and a saved feed still loads with its filters applied.

A position that had never produced a single intro said "Ready for more intros?", and pressing Generate escalated that to "You've actioned all your intros! Great job."

Both credited you with work you hadn't done, and neither told you the one thing worth knowing: whether anybody matches the role.

Improvements

• Why there are no intros: An empty list now says nothing matches this position yet, and names the two things that usually change that, work type and salary range, with a link straight to the position. Of 908 positions running an intro agent, 854 have live intros, 53 have never produced one and exactly one had genuinely been worked through. The old copy was wrong for 53 of those 54 empty cases.

• Generating the first set: A position's first list only appeared once the overnight job reached it, and that job doesn't run at weekends. 72 live positions were sitting in that state. Generate intros is now the main button on the empty state and runs there and then.

Fixes

• A page that loads: A single position pointing at a listing cord couldn't resolve took the whole Intros page down, on every reload, which left the account with nothing to work from. The page now renders and the problem position is logged instead.

• Long position names: A long position title spilled out of the selector and over the buttons beside it. The selector is capped and long titles truncate. The empty state was also rendering behind the top navigation with its illustration cut off, and now clears it.

One company user received 20 message request emails over a weekend. Their notification settings showed no positions selected at all.

Those emails went to everyone at a company and were then trimmed down by each person's position preferences. If someone had no preferences stored, there was nothing to trim, so they got everything. This release sorts out who is on the list, and stops the emails that were being dropped on the way out.

Fixes

• Message requests: No stored preferences now means you're not a recipient, rather than a recipient for every position at your company. Around 45,000 preference rows were filled in from the positions people already hold, and newly invited users start muted, then pick up positions when they join a hiring team.

• Chaser emails: Reminders about one unanswered application on one position went to the whole company, so the 40 accounts with nothing stored were getting a chaser for every position going. They now go to the hiring team, plus anyone already in the conversation.

• Replies in a thread you're part of: If you were talking to someone about a position you don't own, your position preferences quietly stopped their replies reaching you. 6 of 221 conversation pairs over 14 days were in that state, 4 of them not on the hiring team. Being in the thread is now enough. Switching new message emails off still switches them off.

• Emails that never arrived: Two templates hit an error while rendering, and a failed render meant the email was never sent and never retried. 29 went missing in 15 days, roughly 2 a day, all of them digests and mention notifications. A comment mention on someone outside a shortlist accounted for 8, and now sends with a link to that person in search.

• A blip in the cache: When cord briefly couldn't read its cached email rules, it read that as "this person has no rules" and dropped every email in flight. It now goes back to the database instead.

• Position preferences on a new role: Creating or updating a position didn't wait for the hiring team's email preferences to save, so a member could end up holding a position with nothing stored against it. That write now finishes before the position is confirmed.

• Unsubscribe in demo emails: Clicking Unsubscribe always landed on "Unsubscribe failed". It works now. Those emails were also printing the redaction placeholder as it was written, so a profile read "Senior Cloud Engineer at Redacted" and "M. Ipsum". They now read "Senior Cloud Engineer" and "M.", with a line explaining that full profiles come with a subscription.

• Dates in emails: Work and education ranges rendered as "-05 '25 - Present". They now read "May '25 - Present".

Five things that were failing quietly. The biggest one switched off live messaging an hour after you logged in, and never mentioned it.

For everyone

• Realtime messaging: An hour after logging in, the connection carrying live messages and notifications started failing and never recovered for the rest of that page's life, with nothing on screen to say so. It was failing on 87% of requests, 234,174 of them against 33,590 that worked, over 7 days. Sessions now renew that connection instead of giving up on it.

For job seekers

• AI messages: You'd watch cord start writing a message, then stop, leaving an empty box and no error. The message had been written every time. Across 6,413 generations in 30 days, not one came back empty, and the app was throwing it away. It only happened from your second message onwards, which is why it was so hard to pin down.

• Direct and external roles: A role could sit in the direct tab badged "Message directly" with a named contact, then open with an "Apply externally" button and no way to message anyone. The role's own setting now decides, whatever the company record says, in all seven places that classify one: the tabs, the counts, the ranking, search cards, your saved and applied positions, the company name in search, and the position page.

For companies

• Message requests that wouldn't open: A request from someone with no location on their profile crashed the page, so it sat there unread and couldn't be accepted or turned down. 21 active profiles were on that empty location record, along with roughly 9,240 passive ones.

• Feeds with a deleted position: Deleting a position left your feeds and their AI summaries still pointing at it, and the feed then showed "We couldn't load this" on every single load. A deleted position now drops out of the summary dropdown, and deleting one clears the summaries and feed references behind it.

A role open in three cities had one field to say so. It named one city, and the other two ended up in the description where no filter could reach them.

For companies

• Up to five locations: The logistics section of the position form now takes up to five office locations for a single role. Positions you've already posted are untouched.

• Location search: The location inputs suggest cities, postal towns and postcodes alongside street addresses, so you can name a city without having to pick a building inside it.

• In search and matching: The extra cities count everywhere the first one does, so location filters, sorting, the match score, the default feed and how people are ranked for the role all take them into account.

For job seekers

• On the position page: A role based in more than one office shows the main city with the rest behind a short "+2 more", on the position page, the preview and the about-this-position card. Up to three cities show before the rest fold away.

A Boolean search for University of Oxford returned 3,563 people. Two in five of them had studied there.

Whatever you typed into the Boolean box went to a single query over the whole profile as one block of text, which is why the box kept behaving in ways nobody asked for. Five separate faults, all of them measured against the live index of 251,036 people.

Fixes

• Operators: A lowercase or was thrown away as a stopword and the words joined with AND instead, so python or java returned 35,789 people rather than 128,135. A lowercase not did the opposite of what it says: python not java required java. Both now read as what they are, and python not java returns 55,234.

• Universities: University of Oxford matched anyone whose profile mentioned it anywhere. It now reads the schools people actually listed, so 3,563 results at 40% accuracy become 1,412 at 100%. X University, X Uni, Uni of X and the acronyms recruiters type (LSE, UCL, KCL, QMUL, MIT) all resolve to the same place.

• Job titles: Product Manager returned 138,961 people, 12% of whom held the title. It now returns 17,152, all of whom do. Quality Assurance went from 13,660 at 8% to 1,114 at 100%.

• Punctuation: C# and C++ were the same search, both returning 77,160. They now return 37,884 and 29,438. Curly quotes pasted in from a document were also ignored, so the phrase never ran as a phrase.

• Skills are left alone: Deliberately. Of 27,110 results for Kubernetes, 13,234 only mention it in their work history without ticking it as a skill, and those are real matches. Mentioning a skill is evidence you have it. Being named in someone else's job description is not evidence you held their title.

• Saved searches: The repair happens as the search runs, so saved searches and alerts improve without being re-saved. Expect lower counts wherever a search was matching more than it should. That is the fix rather than a regression, but it is worth knowing before the numbers move.