Troubleshooting¶
Use this page when data does not look as expected.
For common user-facing scenarios and how to reason about them, start with Common user problems.
Issue is excluded¶
Common cause: FastSLA did not observe a reliable Start event.
Check:
- the first mapped Start status exists in source history
- the source snapshot status is actually a Start status
- old imported data has been reset/reimported after mapping changes if needed
- the issue filter includes the issue
Imported issue is missing¶
Check:
- source credentials are valid
- the connection test succeeds
- the import job completed
- the issue is inside the import date window
- the issue filter includes the source issue type/priority
- the source status history contains a mapped Start
Import progress looks slow¶
Import progress may spend time scanning source issues before applying issue changes.
For sources with issue count support, the percent is based on handled issues. Change counts are supporting detail.
If many changes are skipped/no-op, FastSLA may be deduplicating already processed history.
What to look for¶
| Symptom | Likely explanation |
|---|---|
| Progress waits before a total appears | The source is being scanned or counted. |
| Progress is indeterminate | The source did not provide an upfront count. |
| Many changes are skipped | Events were duplicates or did not change SLA state. |
| Percent reaches 100% but few issues appear | The imported issues may be excluded by filter or missing Start. |
All events are skipped¶
This usually means FastSLA has already seen equivalent events or they do not produce a state change.
If you expected new issues after a full project reset, check source history, event mapping, and whether the source import is using the intended project/date window.
Webhook returns validation or JSON errors¶
Check that the source sends a JSON body to the expected webhook endpoint and includes the correct project webhook secret.
An empty body or invalid JSON is rejected.
Reports do not match Overview¶
Overview shows current operational attention. Reports measure a selected window.
Differences are expected when:
- issues are terminal and no longer need attention
- issues are running/paused and excluded from completed-measurement percentages
- the report date window does not include the relevant Start
- project filters exclude issues
Lifecycle timeline looks wrong¶
Check:
- whether the graph starts at the first observed Start
- whether the policy is deadline-mode
- whether no-effect statuses are dimmed
- whether targets are in the future and the issue is still running
- whether timestamps are shown in the expected display timezone
Example: breach label placement¶
Breach labels appear below the graph with Now. Start and target labels appear above the graph.
This is only presentation. It does not change SLA calculations.