## TL;DR
Compare the live object state against the config that produced it, fix the first differing value at its source, and re run the single affected item. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

```text
dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York
```

## Use this when
- You see this exact message or symptom in Grafana: dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York
- One run, record, build, or object is affected and you can name it
- A retry without changing anything reproduces the same text

## Not for this skill when
- Grafana fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first

## Steps
1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the live object state, the config value, and the first place the two disagree. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: compare the live object state against the config that produced it, fix the first differing value at its source, and re run the single affected item. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

## Variant phrasings
### dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.
### Grafana version of this failure
The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

## Why it happens
In Grafana, this failure usually means the stored configuration describes the intended setup while the live system has drifted from it. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GfIMiLsFuDkFKrL6HdLgJg