1"use strict";(globalThis.webpackChunk_busyapps_site_busymac=globalThis.webpackChunk_busyapps_site_busymac||[]).push([[2721],{68804(e,t,n){n.r(t),n.d(t,{assets:()=>l,contentTitle:()=>r,default:()=>h,frontMatter:()=>i,metadata:()=>o,toc:()=>d});const o=JSON.parse('{"id":"faqs/why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server","title":"Why Events Could Not Be Stored to the Server","description":"BusyCal may display an alert stating that the following events could not be stored to the server.\\n","source":"@site/docs/faqs/71177-why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server.mdx","sourceDirName":"faqs","slug":"/faqs/71177-why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server","permalink":"/docs/faqs/71177-why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server","draft":false,"unlisted":false,"tags":[],"version":"current","lastUpdatedAt":1788637295000,"sidebarPosition":59000,"frontMatter":{"slug":"71177-why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server","title":"Why Events Could Not Be Stored to the Server","sidebar_label":"Why do I get an error stating that the following events could not be stored to the server?","sidebar_position":59000,"description":"BusyCal may display an alert stating that the following events could not be stored to the server.\\n","keywords":["could not store on server","modified on server","documentation"],"search_applicability":["busycal:mac","busycal:ios"]},"sidebar":"docs","previous":{"title":"Spam calendar invitations","permalink":"/docs/faqs/calendar-spam-invitations"},"next":{"title":"How to set BusyCal and BusyContacts as the default apps","permalink":"/docs/faqs/71161-how-to-set-busycal-and-busycontacts-as-the-default-apps"}}');var s=n(31085),a=n(71184);const i={slug:"71177-why-do-i-get-an-error-stating-that-the-following-events-could-not-be-stored-to-the-server",title:"Why Events Could Not Be Stored to the Server",sidebar_label:"Why do I get an error stating that the following events could not be stored to the server?",sidebar_position:59e3,description:"BusyCal may display an alert stating that the following events could not be stored to the server.\n",keywords:["could not store on server","modified on server","documentation"],search_applicability:["busycal:mac","busycal:ios"]},r=void 0,l={},d=[{value:"Reason 1: Conflict",id:"reason-1-conflict",level:3},{value:"Reason 2: Meeting Cannot be Imported",id:"reason-2-meeting-cannot-be-imported",level:3}];function c(e){const t={a:"a",admonition:"admonition",code:"code",h3:"h3",p:"p",...(0,a.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(t.p,{children:["BusyCal may display an alert stating that ",(0,s.jsx)(t.code,{children:"the following events could not be stored to the server"}),"."]}),"\n",(0,s.jsx)(t.h3,{id:"reason-1-conflict",children:"Reason 1: Conflict"}),"\n",(0,s.jsx)(t.p,{children:"That error occurs when the event you modified in BusyCal is stale and out of sync with the event on the server.\nThis can happen if you are syncing multiple devices or apps with the server and the event was recently modified on another device or\nin another app. When this occurs, the change you made in BusyCal will be rejected by the server and replaced with the copy of the event on the server."}),"\n",(0,s.jsx)(t.h3,{id:"reason-2-meeting-cannot-be-imported",children:"Reason 2: Meeting Cannot be Imported"}),"\n",(0,s.jsxs)(t.p,{children:["You have most likely imported a ",(0,s.jsx)(t.code,{children:".ics"})," meeting file manually and are now seeing this error. This has been ",(0,s.jsx)(t.a,{href:"/docs/faqs/meeting-invitation-faqs/#reason-2-invitation-ics-file-was-manually-imported",children:"explained here in depth"}),"."]}),"\n",(0,s.jsx)(t.admonition,{title:"Avoid Manually Importing .ics Files",type:"tip",children:(0,s.jsx)(t.p,{children:"As a general rule, you should avoid importing .ics files manually when using accounts with iCloud, Google, Outlook etc.\nMeeting invitations show up on your calendar automatically during sync. Whenever an invitation is received, it is captured in two places:\nthe Mail Inbox and the Calendar Inbox. If you import the .ics file sent as an attachment via mail manually, and don't wait for the calendar to\nsync this automatically, conflicts can occur and these can further complicate matters as updates may or may not be sent out correctly. Some servers,\nsuch as Google Calendar, can be extremely picky when it comes to meeting invitations and related conflicts. In the worse case you may also\nend up with duplicate meetings."})})]})}function h(e={}){const{wrapper:t}={...(0,a.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(c,{...e})}):c(e)}},71184(e,t,n){n.d(t,{R:()=>i,x:()=>r});var o=n(14041);const s={},a=o.createContext(s);function i(e){const t=o.useContext(a);return o.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),o.createElement(a.Provider,{value:t},e.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.