Error codes · Task trackers
PULSE-ISSUES-001 The token does not have permission to write to the tracker
What does this mean
You pushed an issue to the Pulse board, and Pulse tried to write its status to GitLab or GitHub where the issue came from. The tracker refused: the token with which Pulse is connected cannot change tasks. The column in Pulse remains the same as you set it, and the note “not recorded in the tracker” is visible on the card.
Why does this happen
- GitLab token issued with scope
read_apiorread_user, but recording requires scopeapi. - GitHub fine-tuned token released without Issues: Read and write access, classic token does not
repo(orpublic_repofor an open repository). - The token is working, but in the project itself you have a role without the right to change tasks (in GitLab below Reporter, in GitHub below Triage).
- The token has expired or been revoked.
What to do
- Click "Open Integrations" and see what token is set for the server of this task.
- Issue a new writable token: GitLab - “Preferences → Access tokens”, scope
api; GitHub - “Settings → Developer settings → Personal access tokens”, “Issues: Read and write” access to the desired repository. - Paste it into “Settings → Integrations” and click “Retry” on the error card or in the taskbar.
If you don’t need to write to the tracker, turn off recording for the project in the taskbar - the “Write to tracker” line.
When to write to support
If the token definitely has write permission, and the refusal is repeated, click “Send report” in the error card: the report will include the tracker’s code and response, the token is hidden in it. Add what server the task is on and click “View and submit.”