Clay S. every time i do a manual update of a source (job search) it replaces the title of the source to the day of the search. Is there any way to avoid this?
When updating a source, you can modify its settings to maintain your preferred title. Here's how: 1. Click on the Source Column in your table 2. Select "Sources" from the menu 3. Click on the source you want to modify 4. Click "Edit source" in the panel that opens on the right 5. Update your settings as needed 6. Click "Submit" to save your changes Additionally, you can set up scheduled updates instead of manual ones to maintain consistency. To do this: ** Click the source column's title ** Under "Sources," select your source ** Choose "On a schedule" under "Run this source" ** Select your preferred frequency (hourly for Enterprise, or daily/weekly/monthly) * Click "Update Source Schedule"
We have reached the limit of automated sources. Each time we manually update a source, it overrides the title of the source.
When manually updating a source, you can maintain your preferred title by following these steps: 1. Click on the Source Column in your table 2. Select "Sources" from the menu 3. Click on the source you want to modify 4. Click "Edit source" in the panel that opens on the right 5. Make sure to keep your preferred title in the settings 6. Click "Submit" to save your changes This way, when you manually update the source, your custom title settings will be preserved.
WE do that, but each time the source is manually updated - it overrides the title with the date of the manual update.
Alex - Do you mind sending the link (url) to the table so we can take a look?
Every single table in our workspace - where there's a manual source - this happens
Alex - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Can i get an official clay slack title of "Beta Product Tester"? π
Hey Alex Haha unfortunately we don't have that yet. That'd be very sweet though! :)
Iβve heard back from our engineering team and can confirm that weβre adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you donβt hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?