PostHog / PostHog/posthog-php

Retry support for non 2xx/3xx

Open
#172 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
33
Forks
34
Avg merge
2d 4h
Merged PRs (30d)
13

Description

Description

The PHP SDK does not retry if the API returns non-2xx and 3xx; 413 is also not an exception
This SDK only retries if there's no connection, timeouts, or network failures
The reason is that the PHP SDK is single-threaded and would slow down the hosting app if the API has outages, etc
For any of those cases, the SDK delivery is best effort and may have data loss

We can do this when we implement https://github.com/PostHog/posthog-php/issues/170

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #170 and the current PHP SDK request and retry path to understand the intended implementation boundary. Verify the behavior for non-2xx and 3xx responses, including 413, while preserving the SDK’s best-effort constraint; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.