Certificate generation process does not directly link the reissue request to the resulting certificate. Workaround: we use certificate issue time to correlate the issuance
Request endpoint often contains stale cached certificate objects (i.e. an embedded certificate object that has status “needs_approval” but the request is “issued”)
@abunashir could you help add additional issues that I missed? Thanks!
Here the issues we encountered:
@abunashir could you help add additional issues that I missed? Thanks!