> Documentation index: https://www.gooddata.ai/docs/gooddata-ui/llms.txt lists every page of these docs as Markdown.

# selectScheduledExportTimezone

- Package: [@gooddata/sdk-ui-dashboard](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/index.md)
- Kind: variable
- Stability: alpha
- Source: https://github.com/gooddata/gooddata-ui-sdk/blob/rel/11.64/libs/sdk-ui-dashboard/src/model/store/meta/metaSelectors.ts

> **Alpha API.** Initial API, highly likely to change outside SemVer. Don't build on it in production. See [API maturity](https://www.gooddata.ai/docs/gooddata-ui/latest/integrations/platform/api-maturity/index.md).
> 

Selects the timezone to store into a scheduled export definition, as a concrete IANA timezone ID.

**Signature:**

```typescript
selectScheduledExportTimezone: DashboardSelector<string | undefined>
```

## Remarks

Unlike [selectEffectiveDashboardTimezone](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.selecteffectivedashboardtimezone/index.md), this returns a value only when the timezone cannot be derived by the backend at schedule run time: when the viewer has an ad-hoc view-mode override active, or when the dashboard is configured with the browser-detected sentinel (the exporter service has no browser to detect from, so the resolution made here must be persisted). When the dashboard has an explicit configured timezone — or none, falling back to workspace or organization settings — this returns undefined and the schedule stores no timezone: the backend reads the dashboard's stored timezone itself, so schedules stay up to date when the dashboard or organization configuration changes without having to be recreated.