Skip to content

Push check: Point the compliance line at a URL that exists The live check's link step caught it: brightdata.com/legal/compliance is a 404. I wrote that path from assumption instead of verifying it. The LinkedIn product page links compliance to brightdata.com/legal-governance, which returns 200. Use that. This is what the link step is for. It ran before any credit was spent, because it sits ahead of the fetch step in the same job. #2

Push check: Point the compliance line at a URL that exists The live check's link step caught it: brightdata.com/legal/compliance is a 404. I wrote that path from assumption instead of verifying it. The LinkedIn product page links compliance to brightdata.com/legal-governance, which returns 200. Use that. This is what the link step is for. It ran before any credit was spent, because it sits ahead of the fetch step in the same job.

Push check: Point the compliance line at a URL that exists The live check's link step caught it: brightdata.com/legal/compliance is a 404. I wrote that path from assumption instead of verifying it. The LinkedIn product page links compliance to brightdata.com/legal-governance, which returns 200. Use that. This is what the link step is for. It ran before any credit was spent, because it sits ahead of the fetch step in the same job. #2