-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client doesn't work with Laravel Queue #30
Comments
Are you calling Sounds like |
Facing the same problem. I have tested calling PostHog::init(config()->get('services.posthog.api_key'), [
'host' => config()->get('services.posthog.host'),
]);
PostHog::capture([
'distinctId' => $this->user->getKey(),
'event' => 'user:registered',
'properties' => [
'registered_via' => $this->registerdVia,
],
]); However it does work when running the job synchronously. |
batch_size as optional parameter solved my problem (we don't have 100 events in time, that's why we didn't catch events in PostHog) |
@nwdles could you show an example? I am confused about that parameter. Do yo mean this? https://posthog.com/docs/api/post-only-endpoints#batch-events |
I mean this |
Hi,
We have this package installed in a Laravel application. The app listens for events for some specific events which are queued and processed in background (through queues). The thing is that when the queued jobs are processed we also submit the events to PostHog, eg:
But we found out that the event is never sent to PostHog. There are no errors, it just does nothing. We tested the same app locally (without queue) and it works as expected. Also we tested making a HTTP request directly to the API through the Guzzle client and it works fine. After some debugging I think there may be some issues with the consumers clients (which by default is
lib_curl
.), and I guess its related to how__destruct
function handles the code within a queued job in Laravel app.Laravel Version 8.75.0
Queue Jobs are processed with the command
php artisan queue:work
.Looking forward to a solution. Thank you.
The text was updated successfully, but these errors were encountered: