Clockify errors
The codes Clockify steps can stop a run with, each with its fix and what happened.
CLOCKIFY_AUTH
A key only works for the workspace it was generated in.
Clockify rejected the API key.
CLOCKIFY_FILE_TOO_LARGE
Ask for a shorter period.
This Clockify report file is larger than a run can carry.
CLOCKIFY_FORBIDDEN
The key's user does not have the role for it in Clockify.
Clockify refused this.
CLOCKIFY_INVALID_CONFIG
Its own reason is in the detail.
A Clockify node's settings do not fit together.
CLOCKIFY_INVALID_HOST
Fix it under Manage → Connections.
The Clockify data region or subdomain on this connection is not one Clockify publishes.
CLOCKIFY_INVALID_REQUEST
Check the ids, the dates and any required custom fields.
Clockify refused the data.
CLOCKIFY_INVALID_RESPONSE
Check the connection.
Clockify answered something that is not JSON.
CLOCKIFY_NOT_FOUND
Clockify knows nothing with that id in this workspace.
CLOCKIFY_NO_USER
Name a user id on the node instead.
Clockify did not say who this API key belongs to.
CLOCKIFY_NO_WORKSPACE
Set the Workspace ID, or fill in the node's override.
This Clockify connection has no workspace to act in.
CLOCKIFY_REQUEST
Check the node's settings.
Clockify refused the request.
CLOCKIFY_RESPONSE_TOO_LARGE
Ask for a smaller page, or a shorter period.
Clockify answered more data than a run can parse.
CLOCKIFY_THROTTLED
A Free workspace gets 30 requests an hour.
Clockify is rate-limiting this workspace.
CLOCKIFY_TOO_MANY_RESULTS
Narrow the period, or read it page by page.
Clockify returned more rows than a run can carry.
CLOCKIFY_UNAVAILABLE
Try again once it is back.
Clockify could not be reached.