Arturo O.

Hey Troy, thanks for reaching out. Appreciate your patience! Took a closer look at the table and tried re-running some of the rows. It appears this may be due to API limits on your Apify account based on the error message it's returning now. Let us know if once it clears up, if you still run into this timing out issue though!

Hey Tim, thanks for reaching out! Thank you for flagging this. Currently, this is expected behavior as the calculation when a 'Limit per Company' is applied the search query still finds associated records within the parameters but in the end it will respect the limit once imported. For example, running a search for "SDR" at xyz.com will query all SDRs but only imports 1 of them in the end. We're actively working on this to improve features and capabilities, and eventually showing an accurate count with all parameters considered. Stay tuned for updates as they come :D

Hey Giorgio, thanks for reaching out and sharing the loom! This makes sense and we certainly have it on the roadmap to incorporate company-level filters for Find Jobs. Stay tuned for updates, but don't have a final ETA just yet! :D

Alrighty, will do! There is a ticket following this issue and have linked this conversation so we can update you as soon as the team confirms it was addressed. Can't say much about an ETA but I've pinged the team for some follow ups. Will keep you posted!

Yup!! Just ran a test in another table and that one ran into the error message. I'll create the ticket or check the status if it's been reported already, appreciate the flag, David.

Oh, I see! Not entirely certain, I wasn't able to reproduce this specific issue related to "required to run", if you run the linkedin waterfall does it let it continue? Also, feel free to share any related issues you run into with clayformatforjson, so we can bring them up with the team

Hey David, thanks for reaching out! Happy to help. Will have to check out why the required to run but I noticed the LinkedIn URL waterfall finder hasn't run yet so maybe it was expecting that flow to determine if Facebook actually existed or not, but can't say the same thing about the instagram column. However, looks like this is an older HTTP template, correct? It's still using the previous HTTP config with JSON.stringify, but the team updated to a new action to better and gracefully handle a lot more edge cases with ClayFormatForJSON -> here's this video on how I quickly updated the column to the current action format if it helps: https://www.loom.com/share/9319afd9ddb24036be24b5d25571fa89