If latest pipeline is deleted API call .../pipelines/latest fails with 403

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

As it stands, API returns 403 if latest pipeline for a branch is deleted, but not only! I found out that the call may return 403 for no reason. Re-try usually solves the problem, but it is obviously not a solution