Skip to content

Limits and troubleshooting

What you see What to do
Power BI keeps asking for credentials, or says “access denied” Check that the user name is exactly export, all lowercase.
“Access denied” and no sign-in window at all Power BI saved the wrong sign-in method. Clear it in Data source settings. See Load data into Power BI.
“Not found” (404) The token expired or was revoked, or the datasource was deleted. Check the token’s status on the API Tokens tab first.
A table is missing in Power BI The datasource doesn’t include it. Edit the datasource and tick the table.
A new custom field doesn’t appear Open Transform data and refresh the preview. A normal refresh doesn’t add new columns.
A large refresh fails partway through Zendesk limits how fast data can be read. Try again later, and see the tips below.
  • The first load takes longest. Power BI reads the data in pages of about 200 rows, so hundreds of thousands of tickets take a while. This is normal.
  • Zendesk allows 100 reads per minute per account. Several big reports refreshing at the same time can hit that limit. Schedule them at different times.
  • Include only the tables you use. Each table is read separately, and Ticket metrics reads all the matching tickets a second time.
  • A refresh that stops for more than an hour has to start over. Zendesk forgets where it was after an hour.

Zendesk search takes a few minutes to catch up. A ticket created or changed in the last few minutes may only show up in the next refresh.

Pick the tickets with the datasource’s ticket filter, and do everything else (filtering columns, sorting, renaming) in Power BI’s Transform data. The feed always sends whole tables, oldest rows first.

Reports show what the person who created the datasource can see in Zendesk. If their role is limited to some groups or organizations, the report includes only those tickets.