Troubleshoot common issues

Most problems come down to which Google account Chrome is using, or the script's "Who has access" setting. Start here — the Help tab in Settings has the same answers.

"Couldn't reach your calendar bridge"

Make sure Chrome is signed in to the Google account that has your calendar, then click Get my key and check your script opens without an error. If you use several Google accounts in Chrome, Google may pick the wrong one; try a Chrome profile that only has this account.

The status says "Not connected" or "Out of date"

Next Up by URLflows checks your calendar every 5 minutes. The status pill in the header shows Connected when all is well, Not connected when the last check failed, and Out of date when it hasn't updated for more than 15 minutes — it keeps trying on its own. Click the status pill to open Settings and check your connection; the line at the bottom of the page shows the error, if there is one.

"Get my key" works but "Load my calendars" can't connect

Your script is probably set to Only myself (or Anyone within your organisation on a work account). Those rely on Google's sign-in cookies, which Brave Shields, Safari and Chrome's "Block third-party cookies" setting block. In Apps Script, go to Deploy → Manage deployments, click the pencil, change Who has access to Anyone, choose Version: New version and deploy. The URL and your key stay the same. On a work account where "Anyone" isn't offered, allow third-party cookies for [*.]google.com instead — see the Workspace guide.

"Key doesn't match"

Click Get my key and paste the key it shows. Keys change when you click Make a new key.

Deploy is greyed out or the app is blocked

On a work or school account, your admin may block Apps Script or limit who can use web apps. Ask your IT team, or use a personal Google account that can see your calendar.

No calendars listed

Next Up sees the same calendars listed in Google Calendar under "My calendars" and "Other calendars". Subscribe to a calendar there first, then click Load my calendars again.

No sound

Chrome keeps a page silent until you click it once — click Turn sound on when it appears. Also check Play a sound when each alert starts is ticked and the volume isn't at 0%.

Flashing is too much

Turn off Flash the page during alerts on the Alerts tab, or click Stop flashing (or Dismiss alert) during an alert.

The pop-out or clean window doesn't open

Chrome has blocked the pop-up. Click the blocked pop-up icon at the right of the address bar, choose to always allow pop-ups for this page, then press P or click the button again. The Google Calendar button's clean window needs the same permission; while pop-ups are blocked, it opens Google Calendar in a new tab instead.

Changed the script?

Use Deploy → Manage deployments, click the pencil, set Version: New version and deploy. That keeps the same URL. A new deployment creates a new URL, which you'd need to paste into Next Up again.

Settings gone

Settings are saved in your browser, separately for each Next Up window. The main window's settings are tied to where the file is saved; extra windows you open from the Windows tab are kept under their window name. If you move or rename the file, switch browsers, or clear browsing data, connect again — your script and URL still work. To update Next Up without losing settings, replace the old file with the new one in the same place and with the same name — see Download and open Next Up for how to check your version. Before moving the file or switching browsers, download a backup from Settings → Backup and restore it afterwards.

Related guides

Walk through setup again in the personal guide or the Workspace guide, or read how your data is handled in Privacy and your calendar data.