330
BMBB91 KMFL 030236
STQMFL

*** spot.weather.gov open request status ***

Note: Please do not ignore this notification. We want to make sure
our customers get their spot forecasts when they want it.

*** Reasons you are getting this alert and solutions ***

1) Around 30 minutes after the deliver date/time, you will get a
   Forecast is Late Notification if a forecast has not been posted
   against a pending spot forecast request. If you post the forecast
   within the next hour, you will no longer get this notification

2) The Customer might have put in a bad deliver date/time and
   a bad Forecast Start date/time. Forecasters should go into the
   spot.weather.gov/cms/admin page, edit the request, fix the
   date/times, save changes, then process changes.

3) The update number in the .TAG line is lower than what is listed
   on the spot.weather.gov/cms/admin page. (.0, .1, .2, etc) The
   solution is to edit the FWS forecast in AWIPS, change the .TAG
   code to the correct update number, and retransmit forecast.

4) You may have posted the forecast against the wrong request.
   Check the code in the .TAG line in the forecast you issued to
   the incident ID in this notification. They should match. Resend
   the forecast with the correct .TAG code.

If you need help, go to new-spot-page-collaboration slack channel.

Below is a list of incidents that are in request pending status and
may need a forecast.

 FO  Incident ID   Forecast Deadline (UTC)              Deadline Incident Name
--- ------------ -------------------------- -------------------- ----------------------------------------
MFL    2517174.0   2025-07-03 02:00:00 UTC           36 min past Shark Valley

Comments and suggestions on this product can be sent to
virgil.middendorf@noaa.gov