- Some event labels are missing.
- Labels that have no free row are hidden rather than drawn over another label, and the status strip counts them ("Labels hidden: 2 (zoom in to see them)"). Zoom in, raise Layout > Max Label Rows per Side, switch Density to Comfortable, or turn off Dates in Labels. Bind an Importance (Optional) measure to decide which labels win the space. Hidden events still have their marker, tooltip and keyboard focus.
- The visual says rows were skipped because Start is not a date.
- Bind the date field itself, not its Date Hierarchy (open the field's menu in the Start well and pick the field name). Start accepts dates, date-times, whole-number years from -9999 to 9999 and text such as 2025-03-14 or c. 1450. Decimal numbers and other text are skipped and counted, never guessed. "End is before Start" rows are skipped the same way.
- Viewers only see three lanes, or no eras.
- More than three lanes, lane groups, eras, the vertical layout and the Roadmap Analysis, Story Mode and Milestone Dates features are premium. In edit mode they preview; in reading view a viewer without a licence sees the first three lanes in your Layout > Lane Order with a "Showing 3 of N lanes" note, in the horizontal layout. Assign the viewer a licence in the Microsoft 365 admin center, or keep the report within three lanes.
- My image does not appear on the event.
- Icon or Image (Optional) takes a built-in icon name (flag, star, rocket, check, alert, team, trophy, factory and others) or an embedded data:image value in base64. Web addresses are never loaded because the visual makes no external calls; such rows are counted in the status strip as "Images from web addresses not shown".
- A reference line or the custom start window does not appear.
- Dates in the Reference Lines card and in Zoom & Navigation > From and To are typed as YYYY-MM-DD, YYYY-MM-DD HH:MM or a whole year (negative = BC). Anything else draws nothing and the status strip shows "Date not recognised". Check that Show Reference Lines is on and, for the window, that Initial Window is set to Custom range.
- Planned dates are matched to the wrong milestones.
- Planned Milestone Dates pair with Milestone Dates by name first: "Launch (Planned)", "Planned Launch" or "Launch plan" pairs with Launch. Fields left over pair by position, and the status strip names those ("Planned dates matched by position, not by name") and any plan with no milestone left. Rename the planned fields in the well so the names match.