Experiments

Refresh Lead Finder

Recompute the lead-finder read model now, instead of waiting for the tick.

Accepted, then done in the background — the work is cohort-sized and an HTTP request is the wrong place for it. Measured 27.08: a full pass over the 197k-lead probe outlived the gunicorn worker's max-requests recycle and came back as a 500 after 83 seconds, having done the work and thrown it away. The cron pass has no such ceiling; only this escape hatch did.

Poll GET …/lead-finder for the result: computed_at is the oldest stamp among the segments, so it moves when the pass has actually landed.

post/api/experiments/{key}/lead-finder/refresh

Request

  • Base URL: https://api.explee.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.explee.com/api/experiments/{key}/lead-finder/refresh
  • Auth: none declared

Path parameters

keystring required

Headers

x-admin-tokenstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 6 revisions of this API.