![🔥 LinkedIn Jobs Scraper avatar](https://images.apifyusercontent.com/mHgGoS_TdUTSnEdIXzBK0OPQfNhRQlCm1O6nG92DEso/rs:fill:92:92/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMuYW1hem9uYXdzLmNvbS9CSHplZlVabFpSS1d4a1Rjay9Ob3BodFR3YmkybXJGdlNxYS1MaW5rZWRJbl9pY29uX2NpcmNsZS5zdmcucG5n.webp)
3 days trial then $29.99/month - No credit card required now
![🔥 LinkedIn Jobs Scraper](https://images.apifyusercontent.com/mHgGoS_TdUTSnEdIXzBK0OPQfNhRQlCm1O6nG92DEso/rs:fill:92:92/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMuYW1hem9uYXdzLmNvbS9CSHplZlVabFpSS1d4a1Rjay9Ob3BodFR3YmkybXJGdlNxYS1MaW5rZWRJbl9pY29uX2NpcmNsZS5zdmcucG5n.webp)
🔥 LinkedIn Jobs Scraper
3 days trial then $29.99/month - No credit card required now
ℹ️ Designed for both personal and professional use, simply enter your desired job title and location to receive a tailored list of job opportunities. Try it today!
If the "postedTime" is in hours, the "publishedAt" is Null
Closed
If the "postedTime" is in hours, the "publishedAt" is Null. Is it possible for you to compute the "publishedAt" based on the difference between the run time and hours since posted?
alizarin_olive
Hi Ashley Copp,
Thank you for opening the issue and suggesting the addition of a computed "publishedAt" based on the difference between the run time and hours since the job was posted. We appreciate your valuable suggestion!
This feature aligns well with our goal of improving the actor's capabilities, and we are already working on implementing it. Rest assured that we will add this functionality as soon as possible to provide more accurate and helpful data.
We'll keep you updated on the progress, and if you have any further questions or ideas, please feel free to share them with us.
Thanks again for your input!
Best regards, The Bebity team
testtheworkout
Hey team, any update on this?
![bebity avatar](https://apify-image-uploads-prod.s3.amazonaws.com/NtSyuueLA59W6ukLM/pHNg7Z3QSj9uGGLYT-bebity_logo_%281%29.png)
Hi @testtheworkout,
Thank you for your patience and for following up on this issue.
We are pleased to inform you that we have just deployed a fix for this issue. You should now receive the publishedAt field accurately, even when the postedTime is in hours.
If you encounter any further issues or have any questions following this fix, please feel free to open a new issue.
Thank you for your continued support!
Best regards, The Bebity Team
- 318 monthly users
- 18 stars
- 100.0% runs succeeded
- 2.2 days response time
- Created in Feb 2023
- Modified 28 days ago