Support for Problem Links
Email support@aldorock.com. We answer within one business day, Monday to Friday 09:00 to 17:00 Central European Time.
What to include
- Your Zendesk subdomain (for example
yourcompany.zendesk.com). - The ticket numbers involved: the problem, and an incident if it is about one.
- What you did, what you expected, what happened, and the exact message the panel showed.
Please do not send ticket content or customer data; the numbers are enough.
Common questions
"Zendesk refused this action: your role is not allowed to change these tickets (403)"
Your agent role may not edit some of the tickets, for example tickets in a group you cannot see. Ask an admin to check your role, or ask an agent with access to run the bulk action.
"Zendesk rejected the change … (422)"
A ticket rule blocked the change, and the message says which. A typical cause is a field that must be filled in before a ticket is solved.
"#… is no longer a problem ticket"
Someone changed the type of the problem this incident is linked to. Zendesk allows that and leaves the incidents linked to it, but solving it no longer solves them. Use Change problem to link the incident to the right problem, or Unlink.
"Zendesk is rate limiting requests right now"
Your account has used its API limit for the minute, often because of other apps or integrations. Wait a moment and try again; a bulk action that already started keeps running in Zendesk.
Some incidents failed in a bulk action
The message lists them with Zendesk's reason. Closed tickets are always skipped because Zendesk does not allow changes to them.
"… incidents were not changed (#… to #…)"
Zendesk refused to start part of the run, for example because too many background jobs were already running for your account. The incidents named were not touched. Running the action again later applies it to all incidents again: harmless for a status change, but a note would be added a second time to the ones that already have it, so use a status filter where that helps.
"Zendesk is still working on …"
The jobs keep running in Zendesk. Open the problem again later in the same browser and the app shows the result.
"Someone else changed this ticket at the same moment (409)"
Two changes reached Zendesk together. Reload the ticket and try again.
Copy as CSV does nothing
Some browsers block the clipboard inside apps. The panel then shows the CSV in a text box; select it and copy it yourself.
Service status
The app runs in your browser and talks only to Zendesk. Zendesk incidents are on status.zendesk.com.
