Now

Expired requests sort by when they expired

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.

A profile that keeps itself up to date

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.

Allow saving of long job descriptions

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.

Intros that start when your role 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.