{"id":5578,"date":"2026-03-25T22:09:09","date_gmt":"2026-03-25T16:39:09","guid":{"rendered":"https:\/\/blog.spike.sh\/?p=5578"},"modified":"2026-04-03T21:02:05","modified_gmt":"2026-04-03T15:32:05","slug":"on-call-schedules-not-rotating-on-gap-based-schedules","status":"publish","type":"post","link":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/","title":{"rendered":"On-call schedules not rotating on gap-based schedules"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">On March 25, 2026, a user reported that their on-call schedule was not rotating correctly. The person who had just finished their shift remained shown as on-call, even though the next shift hadn&#8217;t started yet and nobody was supposed to be on-call during that gap. We identified the root cause, deployed a fix, and on-call schedules now rotate correctly for all schedule types.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Some teams configure on-call schedules with intentional gaps \u2014 for example, a schedule where someone is on-call only at night, with no coverage during the day. When one shift ended and the next shift hadn&#8217;t started yet, the outgoing person should have been marked off-call. Instead, they remained active.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The result: the previous on-call person kept receiving alerts during a period they weren&#8217;t supposed to be on-call, and the schedule appeared stuck.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Impact<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Customers with gap-based schedules were affected. The previous on-call person continued receiving alerts during periods when no one was supposed to be on-call, and the schedule appeared to not be rotating.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<style>\n.pm-timeline-wrap { max-width: 720px; margin: 0 auto; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; }\n.pm-tl-heading { font-size: 15px; font-weight: 600; color: #111; margin: 0 0 0.75rem; padding-bottom: 0.5rem; border-bottom: 1px solid #e5e5e5; }\n.pm-timeline { list-style: none; padding: 0; margin: 0; position: relative; }\n.pm-timeline::before { content: ''; position: absolute; left: 72px; top: 6px; bottom: 6px; width: 1px; background: #e5e5e5; }\n.pm-timeline li { display: flex; gap: 1.5rem; margin-bottom: 1.25rem; position: relative; }\n.pm-tl-time { font-size: 12px; font-weight: 600; color: #888; min-width: 60px; text-align: right; padding-top: 2px; font-variant-numeric: tabular-nums; }\n.pm-tl-dot { width: 8px; height: 8px; border-radius: 50%; background: #ccc; margin-top: 5px; flex-shrink: 0; position: relative; z-index: 1; }\n.pm-tl-dot.fix { background: #1D9E75; }\n.pm-tl-content { font-size: 14px; color: #555; line-height: 1.6; }\n.pm-tl-content strong { color: #111; font-weight: 600; }\n<\/style>\n\n<div class=\"pm-timeline-wrap\">\n  <p class=\"pm-tl-heading\">Timeline <span style=\"font-size:12px; font-weight:400; color:#888;\">UTC, March 25, 2026<\/span><\/p>\n  <ul class=\"pm-timeline\">\n    <li>\n      <span class=\"pm-tl-time\">12:25 PM<\/span>\n      <span class=\"pm-tl-dot\"><\/span>\n      <span class=\"pm-tl-content\">A user reports via live chat that their on-call schedule appears stuck, the same person is shown as on-call across a gap where no one should be on-call.<\/span>\n    <\/li>\n    <li>\n      <span class=\"pm-tl-time\">1:50 PM<\/span>\n      <span class=\"pm-tl-dot\"><\/span>\n      <span class=\"pm-tl-content\">Our team begins investigation into the on-call scheduling engine.<\/span>\n    <\/li>\n    <li>\n      <span class=\"pm-tl-time\">~2:15 PM<\/span>\n      <span class=\"pm-tl-dot\"><\/span>\n      <span class=\"pm-tl-content\"><b>Root cause identified:<\/b> a code change pushed two weeks prior introduced a condition that skipped ending the current shift if the same person was to be on-call next.<\/span>\n    <\/li>\n    <li>\n      <span class=\"pm-tl-time\">2:31 PM<\/span>\n      <span class=\"pm-tl-dot fix\"><\/span>\n      <span class=\"pm-tl-content\"><strong>Fix deployed.<\/strong> On-call schedules now rotate correctly, including for gap-based configurations.<\/span>\n    <\/li>\n  <\/ul>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Root cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Two weeks ago, we shipped a change to avoid sending redundant shift-end notifications when the same person&#8217;s shift was simply continuing. The intent was: if Person A&#8217;s shift ends and A is immediately starting the next shift, don&#8217;t notify them that they&#8217;ve gone off-call and back on-call.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The implementation checked whether the user was changing before ending the current shift. This worked correctly when transitioning between two different people but it had a blind spot: when a shift ends and\u00a0<strong>no new shift is starting<\/strong>\u00a0(i.e., a gap in the schedule), there&#8217;s no &#8220;next user&#8221; to compare against. The condition was never satisfied, so the shift was never ended.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n<div class=\"wp-block-code\">\n\t<div class=\"cm-editor\">\n\t\t<div class=\"cm-scroller\">\n\t\t\t\n<pre>\n<code class=\"language-javascript\"><div class=\"cm-line\"><span class=\"tok-keyword\">if<\/span> <span class=\"tok-punctuation\">(<\/span><span class=\"tok-variableName\">currentShiftToBeEnded<\/span><span class=\"tok-punctuation\">)<\/span> <span class=\"tok-punctuation\">{<\/span><\/div><div class=\"cm-line\">  <span class=\"tok-variableName\">userIsChanging<\/span> <span class=\"tok-operator\">=<\/span> <span class=\"tok-variableName\">currentUser<\/span> <span class=\"tok-operator\">!=<\/span> <span class=\"tok-variableName\">nextUser<\/span><\/div><div class=\"cm-line\">  <span class=\"tok-keyword\">if<\/span> <span class=\"tok-punctuation\">(<\/span><span class=\"tok-variableName\">userIsChanging<\/span><span class=\"tok-punctuation\">)<\/span> <span class=\"tok-punctuation\">{<\/span> <span class=\"tok-comment\">\/\/ &lt;-- root cause<\/span><\/div><div class=\"cm-line\">    <span class=\"tok-variableName\">endShift<\/span><span class=\"tok-punctuation\">(<\/span><span class=\"tok-variableName\">currentShiftToBeEnded<\/span><span class=\"tok-punctuation\">)<\/span><\/div><div class=\"cm-line\">  <span class=\"tok-punctuation\">}<\/span><\/div><div class=\"cm-line\"><span class=\"tok-punctuation\">}<\/span><\/div><\/code><\/pre>\n\t\t<\/div>\n\t<\/div>\n<\/div>\n\n\n<p class=\"wp-block-paragraph\">The fix: always end the current shift when it&#8217;s due to end, regardless of who (if anyone) is coming on next. Shift-end and shift-start are now treated as independent events.<\/p>\n\n\n<div class=\"wp-block-code\">\n\t<div class=\"cm-editor\">\n\t\t<div class=\"cm-scroller\">\n\t\t\t\n<pre>\n<code class=\"language-javascript\"><div class=\"cm-line\"><span class=\"tok-keyword\">if<\/span> <span class=\"tok-punctuation\">(<\/span><span class=\"tok-variableName\">currentShiftToBeEnded<\/span><span class=\"tok-punctuation\">)<\/span> <span class=\"tok-punctuation\">{<\/span><\/div><div class=\"cm-line\">    <span class=\"tok-variableName\">endShift<\/span><span class=\"tok-punctuation\">(<\/span><span class=\"tok-variableName\">currentShiftToBeEnded<\/span><span class=\"tok-punctuation\">)<\/span><\/div><div class=\"cm-line\"><span class=\"tok-punctuation\">}<\/span><\/div><\/code><\/pre>\n\t\t<\/div>\n\t<\/div>\n<\/div>\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Lessons learned<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Gap schedules weren&#8217;t covered enough in our test cases.<\/strong>\u00a0The change was tested against standard rotation scenariosbut not against schedules with intentional gaps i.e. A \u2192 <em>Gap<\/em> \u2192 A. We&#8217;re adding explicit test coverage for gap-based, night-only, and partial-day schedule types.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On-call rotation test cases<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A \u2192 A <\/li>\n\n\n\n<li>A \u2192 B<\/li>\n\n\n\n<li>A \u2192 <em>gap<\/em> \u2192 B<\/li>\n\n\n\n<li>A \u2192 <em>gap<\/em> \u2192 A<\/li>\n\n\n\n<li>A \u2192 <em>end<\/em> later<\/li>\n\n\n\n<li><em>scheduled start<\/em> \u2192 <em>A<\/em><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Shift lifecycle events should be independent.<\/strong>\u00a0Ending a shift and starting a new one are two separate concerns. Coupling them \u2014 even with good intent \u2014 creates fragile logic. The on-call engine should treat each lifecycle event atomically.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On-call schedules with gaps between shifts now rotate correctly. If you&#8217;re using a schedule where nobody is on-call during certain hours, your rotations will work as configured. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thanks for reading. We continue on our mission to build a very flexible on-call for everyone \ud83d\ude42 <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>On March 25, 2026, a user reported that their on-call schedule was not rotating correctly. The person who had just finished their shift remained shown as on-call, even though the next shift hadn&#8217;t started yet and nobody was supposed to be on-call during that gap. We identified the root cause, deployed a fix, and on-call [&hellip;]<\/p>\n","protected":false},"author":263547071,"featured_media":5723,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_wpcom_ai_launchpad_first_post":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":true,"token":"eyJpbWciOiJodHRwczpcL1wvYmxvZy5zcGlrZS5zaFwvd3AtY29udGVudFwvdXBsb2Fkc1wvMjAyNlwvMDNcL3Bvc3Rtb3J0ZW0tb24tY2FsbC1nYXBzLTEwMjR4NTU1LnBuZyIsInR4dCI6Ik9uLWNhbGwgc2NoZWR1bGVzIG5vdCByb3RhdGluZyBvbiBnYXAtYmFzZWQgc2NoZWR1bGVzIiwidGVtcGxhdGUiOiJoaWdod2F5IiwiZm9udCI6IiIsImJsb2dfaWQiOjIzMzEzODkwMH0.rIv6ImF4vucrqRmLpTDSgTdb1f1n0-v43-YzJtcY0VMMQ"},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[1444],"tags":[],"class_list":["post-5578","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postmortem"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>On-call schedules not rotating on gap-based schedules - Welcome to Spike.<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"On-call schedules not rotating on gap-based schedules - Welcome to Spike.\" \/>\n<meta property=\"og:description\" content=\"On March 25, 2026, a user reported that their on-call schedule was not rotating correctly. The person who had just finished their shift remained shown as on-call, even though the next shift hadn&#8217;t started yet and nobody was supposed to be on-call during that gap. We identified the root cause, deployed a fix, and on-call [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/\" \/>\n<meta property=\"og:site_name\" content=\"Welcome to Spike.\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-25T16:39:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-03T15:32:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1040\" \/>\n\t<meta property=\"og:image:height\" content=\"564\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Damanpreet\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Damanpreet\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/\"},\"author\":{\"name\":\"Damanpreet\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/4bc971837058eacf02e9ef12fb625155\"},\"headline\":\"On-call schedules not rotating on gap-based schedules\",\"datePublished\":\"2026-03-25T16:39:09+00:00\",\"dateModified\":\"2026-04-03T15:32:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/\"},\"wordCount\":551,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/postmortem-on-call-gaps.png\",\"articleSection\":[\"Postmortem\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/\",\"name\":\"On-call schedules not rotating on gap-based schedules - Welcome to Spike.\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/postmortem-on-call-gaps.png\",\"datePublished\":\"2026-03-25T16:39:09+00:00\",\"dateModified\":\"2026-04-03T15:32:05+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/4bc971837058eacf02e9ef12fb625155\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/postmortem-on-call-gaps.png\",\"contentUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/postmortem-on-call-gaps.png\",\"width\":1040,\"height\":564,\"caption\":\"Spike.sh postmortem on on-call schedules not rotating for gaps\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/on-call-schedules-not-rotating-on-gap-based-schedules\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.spike.sh\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"On-call schedules not rotating on gap-based schedules\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/\",\"name\":\"Welcome to Spike.\",\"description\":\"In this space, our team talks about all things incidents, response, oncall, and share our journey of building Spike.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.spike.sh\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/4bc971837058eacf02e9ef12fb625155\",\"name\":\"Damanpreet\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g\",\"caption\":\"Damanpreet\"},\"url\":\"https:\\\/\\\/blog.spike.sh\\\/author\\\/daman50ab08d672\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"On-call schedules not rotating on gap-based schedules - Welcome to Spike.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/","og_locale":"en_GB","og_type":"article","og_title":"On-call schedules not rotating on gap-based schedules - Welcome to Spike.","og_description":"On March 25, 2026, a user reported that their on-call schedule was not rotating correctly. The person who had just finished their shift remained shown as on-call, even though the next shift hadn&#8217;t started yet and nobody was supposed to be on-call during that gap. We identified the root cause, deployed a fix, and on-call [&hellip;]","og_url":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/","og_site_name":"Welcome to Spike.","article_published_time":"2026-03-25T16:39:09+00:00","article_modified_time":"2026-04-03T15:32:05+00:00","og_image":[{"width":1040,"height":564,"url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","type":"image\/png"}],"author":"Damanpreet","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Damanpreet","Estimated reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#article","isPartOf":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/"},"author":{"name":"Damanpreet","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/4bc971837058eacf02e9ef12fb625155"},"headline":"On-call schedules not rotating on gap-based schedules","datePublished":"2026-03-25T16:39:09+00:00","dateModified":"2026-04-03T15:32:05+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/"},"wordCount":551,"commentCount":0,"image":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","articleSection":["Postmortem"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/","url":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/","name":"On-call schedules not rotating on gap-based schedules - Welcome to Spike.","isPartOf":{"@id":"https:\/\/blog.spike.sh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#primaryimage"},"image":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","datePublished":"2026-03-25T16:39:09+00:00","dateModified":"2026-04-03T15:32:05+00:00","author":{"@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/4bc971837058eacf02e9ef12fb625155"},"breadcrumb":{"@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#primaryimage","url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","contentUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","width":1040,"height":564,"caption":"Spike.sh postmortem on on-call schedules not rotating for gaps"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.spike.sh\/on-call-schedules-not-rotating-on-gap-based-schedules\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.spike.sh\/"},{"@type":"ListItem","position":2,"name":"On-call schedules not rotating on gap-based schedules"}]},{"@type":"WebSite","@id":"https:\/\/blog.spike.sh\/#website","url":"https:\/\/blog.spike.sh\/","name":"Welcome to Spike.","description":"In this space, our team talks about all things incidents, response, oncall, and share our journey of building Spike.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.spike.sh\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Person","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/4bc971837058eacf02e9ef12fb625155","name":"Damanpreet","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9a938d08ab9251a99e241686ddce63028cca486f4937fffad851519903da88d3?s=96&d=robohash&r=g","caption":"Damanpreet"},"url":"https:\/\/blog.spike.sh\/author\/daman50ab08d672\/"}]}},"modified_by":"Sreekar","jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/postmortem-on-call-gaps.png","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfMe4Q-1rY","_links":{"self":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5578","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/users\/263547071"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/comments?post=5578"}],"version-history":[{"count":18,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5578\/revisions"}],"predecessor-version":[{"id":5722,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5578\/revisions\/5722"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media\/5723"}],"wp:attachment":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media?parent=5578"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/categories?post=5578"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/tags?post=5578"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}