Handling a Frozen Maintenance Request App | Learn Korean in English

Sentence explanations

1. 시설 관리 요청 앱이 보내기를 누른 뒤 멈췄어.

   The maintenance request app froze after I pressed send.

   시설

   facilities

   관리

   maintenance

   요청

   request

   앱

   app

   보내기

   sending

   누른

   pressed

   뒤

   after

   멈췄어

   froze

   More detail

   시설 means “facility” or “facilities.” Here it forms a compound with 관리, giving the area of facility maintenance or management. The word itself is a noun; it is not the word meaning “maintenance” by itself. 관리 is a noun meaning “management,” “maintenance,” or “care,” depending on what is being managed. In 시설 관리, it specifies maintenance/management of facilities. Korean commonly combines nouns this way: the first noun narrows the area of the second. 요청 means “request.” It is a noun and can be used in compounds such as 관리 요청 (“maintenance request”). Example: 요청을 보냈어요. — “I sent a request.” 앱 is the ordinary shortened loanword for “app/application.” 시설 관리 요청 앱 is a noun sequence: “facility-maintenance-request app,” naturally understood here as “the app for facility maintenance requests.” Korean often places modifying nouns before the noun they describe. 보내기 means “sending” here, specifically the “Send” action or button. It is formed from the verb 보내다 (“to send”) plus -기, which turns a verb into a noun-like form. The same pattern is reusable: 저장하기 means “saving” or “Save,” from 저장하다 (“to save”). 누른 means “pressed” in the modifying form of 누르다 (“to press”). The form 누르다 → 누른 describes a completed action before a following noun or construction. Here it belongs with the omitted object of the action, 보내기: pressing Send. Korean does not mark the omitted subject here; the fixed translation identifies that the speaker pressed it. 뒤 means “after” when used in a time expression. The pattern 동작-기 뒤 means “after doing [the action],” so 보내기를 누른 뒤 means “after pressing Send.” 뒤 is a noun-like word, and the preceding phrase specifies the event whose later point it marks. Example: 식사한 뒤 쉬었어요. — “I rested after eating.” 멈췄어 means “froze” or “stopped responding” in this context. Its base verb is 멈추다 (“to stop”); 멈췄어 is the informal conversational past form. The subject is 앱이, so the app is the thing that stopped responding, not the speaker. The ending -어 gives a casual spoken style; a more polite past form is 멈췄어요. Putting the chunks together, 시설 관리 요청 앱이 identifies the app as the subject, 보내기를 누른 뒤 sets the time as after the speaker pressed Send, and 멈췄어 states that the app then froze. The complete meaning is: “The maintenance request app froze after I pressed send.”

2. 다시 시도하기 전에 네 기록에 요청이 나타나는지 확인해 봐.

   Check whether the request appears in your history before you try again.

   다시

   again

   시도하기 전에

   before trying

   네

   your

   기록

   history

   요청

   request

   나타나는지

   whether it appears

   확인해 봐

   check and see

   More detail

   다시 means “again” and modifies the later action. It marks repetition of trying, not repetition of checking. A reusable example is 다시 읽어 봐. — “Read it again.” 시도하기 전에 means “before trying.” The verb is 시도하다 (“to try”); 시도하기 uses -기 to turn the verb into an action phrase, and 전에 places the next event before that action. This pattern is reusable: 자기 전에 물을 마셔. — “Drink water before going to bed.” 네 is the informal possessive form meaning “your.” It identifies the record as belonging to the person being addressed. It is distinct from 내 (“my”), as in 내 기록 — “my history.” 기록 means “record” or “history.” Here it refers to the addressee’s history, as indicated by 네 기록. In another context, the same noun can refer more generally to a record or written account. 요청 means “request.” In this sentence it is the request that may be present in the history. The noun can also be used in compounds such as 유지 보수 요청 (“maintenance request”), as in the preceding context. 나타나는지 means “whether it appears.” The verb is 나타나다 (“to appear”); 나타나는지 combines its present form with -는지, which marks an embedded yes-or-no question. The form asks whether the request appears, rather than asserting that it does. For example, 문제가 나타나는지 확인해. — “Check whether the problem appears.” 확인해 봐 means “check and see.” 확인하다 means “to check” or “to verify,” and -아/어 보다 adds the idea of trying an action or checking by experience. Here 봐 is the informal command form of 보다 in this construction, so the expression is a casual instruction to check. A more formal version would use a formal request ending rather than -해 봐. Together, 다시 시도하기 전에 sets the time condition: first, before trying again. 네 기록에 identifies the addressee’s history as the place where the request may appear; 에 marks that location. 요청이 나타나는지 makes “whether the request appears” the content being checked, with 이 marking 요청 as the subject of 나타나다. The final 확인해 봐 gives the casual instruction. Thus the whole utterance means: “Check whether the request appears in your history before you try again.”

3. 아직 로딩 중이라서 메시지가 전송됐는지 알 수가 없어.

   It is still loading, and I cannot tell if the message went through.

   아직

   still; yet

   로딩 중이라서

   because it is loading

   메시지

   message

   전송됐는지

   whether it was sent

   알 수가 없어

   cannot tell

   More detail

   아직 means “still” here: the loading has not finished at the relevant time. It commonly appears with an ongoing or not-yet-completed situation. For example, 아직 안 끝났어 means “It isn’t finished yet.” 로딩 중이라서 gives the reason. 로딩 중 means “in the middle of loading,” and -이라서 attaches to the noun-based expression 로딩 중 to mean “because it is ….” The form 이라서 is used after a consonant-final noun; after a vowel-final noun, the corresponding form is 라서. Here, the reason is the ongoing loading state, not the message itself. -아서/어서 is another common way to connect a reason to a result, with its form determined by the preceding expression. 메시지 is “message.” It is a noun and can be reused with particles such as 메시지가 (“the message” as the subject) or 메시지를 (“the message” as the object). The sentence does not specify a particular kind of message beyond the context. 전송됐는지 asks whether the message was sent or transmitted. The observed form is based on 전송되다, “to be sent/transmitted”: 전송되다 → past 전송됐다; before -는지, this becomes 전송됐는지. -는지 marks an embedded question or uncertainty, comparable to “whether.” It is the sending that is uncertain here, not the identity of the message. For example, 파일이 전송됐는지 확인해 봐 means “Check whether the file was sent.” 알 수가 없어 means “cannot tell” or “cannot know.” 알다 means “to know,” and 알 수 있다/없다 is a reusable pattern meaning “can/cannot know” or, more literally, “there is/is not a way to know.” The 가 in 수가 is the subject particle attached to 수; it is not part of the verb 알다. The ending 없어 is an informal plain-style form of 없다, suitable for speech with a familiar addressee. For example, 지금은 알 수가 없어 means “I can’t tell right now.” Together, 아직 로딩 중이라서 says that the system is still in the process of loading, 메시지가 전송됐는지 identifies the uncertain question—whether the message was sent—and 알 수가 없어 says that the speaker cannot determine the answer. The complete meaning is: “It is still loading, and I cannot tell if the message went through.”

4. 문제를 분명하게 설명할 수 있게 화면을 캡처해 둬.

   Take a screenshot so you can explain the problem clearly.

   문제

   problem

   분명하게

   clearly

   설명할

   explain

   수 있게

   so that one can

   화면

   screen

   캡처해 둬

   capture and keep it ready

   More detail

   문제 means “problem” here. Its base noun is 문제, and 문제를 marks it as the object of the action with the object particle 를. The sentence therefore treats the problem as what will be explained. 분명하게 means “clearly.” It is the adverbial form of 분명하다 (“to be clear”); the ending -게 lets the descriptive word modify the verb 설명하다. Compare 분명한 설명 (“a clear explanation”), where the related form modifies a noun instead. 설명할 comes from 설명하다, “to explain.” The ending -ㄹ makes the verb modify the following 수 in 설명할 수, a pattern meaning “can explain” or “be able to explain.” Here it is not a completed-past form; it presents explaining as a possible action. 수 있게 completes the pattern -ㄹ 수 있게, “so that [someone] can …” or “in a way that makes … possible.” 수 expresses possibility or ability, while 있게 is the adverbial form of 있다 (“to exist/be”) and connects this purpose to the next action. A reusable example is 읽을 수 있게 크게 써 줘 — “Write it large enough so I can read it.” 화면 means “screen.” In this sentence it identifies what is captured. It is a noun and can be used in compounds or phrases such as 화면을 보다 (“look at the screen”). The object marking for this noun is supplied by the following 을 in 화면을. 캡처해 둬 is an informal instruction built from 캡처하다 (“to capture,” especially a screen image), followed by -아/어 두다. 캡처해 두다 means to capture something and leave it saved or ready for later use. 둬 is the contracted informal imperative form of 두어, so the utterance asks the listener to do this. For example, 주소를 적어 둬 means “Write the address down and keep it noted.” Together, 문제를 분명하게 설명할 수 있게 gives the purpose: making it possible to explain the problem clearly. 화면을 캡처해 둬 instructs the listener to capture the screen and keep the capture available. Thus the whole utterance means, “Take a screenshot so you can explain the problem clearly.”

5. 같은 요청을 다시 보내고 싶지는 않아.

   I do not want to send the same request again.

   같은

   same

   요청

   request

   다시

   again

   보내고 싶지는 않아

   do not want to send

   More detail

   같은 means “the same” here and describes 요청. It is the form used before a noun: 같은 요청 = “the same request.” 요청 is a noun meaning “request.” It can combine with verbs such as 요청을 보내다 (“send a request”), as in this sentence. 다시 is an adverb meaning “again” or “once more.” Its position before the verb phrase shows that the sending would be repeated: 다시 보내다 = “send again.” 보내고 싶지는 않아 expresses “do not want to send.” The useful pattern is verb stem + 고 싶다 for “want to do”: 보내다 (“to send”) becomes 보내고 싶다 (“want to send”). Here 보내고 싶지는 않다 uses -지는 않다 to negate that desire, with a contrastive sense such as “as for wanting to send it, I do not.” 않아 is the informal plain form of 않다 in this ending. Together, 같은 요청을 marks “the same request” as what would be sent, 다시 adds repetition, and 보내고 싶지는 않아 says that the speaker does not want to send it. The whole utterance means: “I do not want to send the same request again.”

6. 잠깐 기다렸다가 새 요청을 시작하기 전에 앱을 확인해 봐.

   Wait a short time, then check the app before starting a new request.

   잠깐

   for a short while

   기다렸다가

   wait, then

   새

   new

   요청

   request

   시작하기 전에

   before starting

   앱

   app

   확인해 봐

   try checking

   More detail

   잠깐 means “for a short while” here. It is an adverb, so it modifies the waiting rather than naming a length as a noun. Example: 잠깐 쉬어요. — “Let’s rest for a short while.” 기다렸다가 comes from 기다리다, “to wait,” with the connective form -았다가. In this sentence it presents waiting as the first action and then moves to the next action: “wait, then …”. The subject is understood from context rather than repeated. Example: 여기서 기다렸다가 같이 가요. — “Wait here, then let’s go together.” 새 means “new” and appears before the noun it describes. It is the attributive form used with a noun; unlike some descriptive forms, 새 does not change for number or gender. Example: 새 계획을 세웠어요. — “I made a new plan.” 요청 means “request.” It is a noun and can combine with particles such as 을/를 when it is the object of an action. In the fixed sentence, 새 요청 is “a new request,” with 새 describing 요청. 시작하기 전에 means “before starting.” 시작하다 means “to start”; -기 turns the verb into an action-noun-like form, and 전에 means “before.” The pattern 동사-기 전에 is reusable for “before doing …”. Example: 자기 전에 물을 마셔요. — “I drink water before going to sleep.” 앱 means “app,” a noun referring here to the application that should be checked. The object particle 을 follows it in the full sentence: 앱을. 확인해 봐 means “try checking.” 확인하다 means “to check” or “to verify,” and 봐 here is the auxiliary use of 보다, “to try doing something,” not a separate request to look at something. The ending -아/어 봐 makes an informal plain-style suggestion or command: 동사-아/어 봐 means “try doing …”. Example: 다시 확인해 봐. — “Try checking again.” Together, 잠깐 기다렸다가 gives the sequence “wait for a short while, then”; 새 요청을 시작하기 전에 means “before starting a new request”; and 앱을 확인해 봐 means “try checking the app.” The complete utterance therefore means: “Wait a short time, then check the app before starting a new request.”

7. 계속 멈추면 건물 관리팀에 직접 연락해야 할까?

   If it still freezes, should I contact building maintenance directly?

   계속

   still; continuously

   멈추면

   if it freezes/stops

   건물

   building

   관리팀

   maintenance team

   직접

   directly

   연락해야 할까?

   should I contact ...?

   More detail

   계속 means that the situation continues or happens repeatedly. It can modify a verb to give a sense such as “still” or “ 계속.” Here it says that the freezing has not stopped. 멈추면 is the conditional form of 멈추다, “to stop” or, for an app or process, “to freeze.” The ending -면 makes an “if/when” condition: 멈추다 → 멈추면, “if it stops/freezes.” In this sentence, the understood subject is the app or process mentioned in the surrounding context. 건물 means “building.” It is a noun that can modify another noun directly, as in 건물 관리팀, “building maintenance team.” 관리팀 means “maintenance team” here. 관리 refers to management or maintenance, and 팀 means “team”; together, the compound identifies the team responsible for the building’s management or maintenance. 직접 means “directly” or “in person.” It indicates that the speaker would make contact with the maintenance team without using an intermediary. For example, 담당자에게 직접 연락해요 means “I contact the person in charge directly.” 연락해야 할까? asks whether the speaker should make contact. 연락하다 means “to contact” or “to get in touch.” In 연락해야, the verb is combined with -아/어야 하다, a pattern expressing that something is required or advisable: 연락해야 하다, “need to/should contact.” The ending -ㄹ까? in 할까? turns this into a deliberative question, roughly “should I ...?” Thus 해야 할까? asks whether that obligation or advisable action applies. The subject is omitted but understood as the speaker, matching “should I” in the translation. Together, 계속 멈추면 sets the condition “if it continues to freeze,” 건물 관리팀에 identifies the team being contacted, and 직접 연락해야 할까? asks whether the speaker should contact that team directly. The whole utterance means: “If it still freezes, should I contact building maintenance directly?”

8. 관리팀에 직접 연락해서 앱이 작동하지 않을 수도 있다고 설명해.

   Contact them directly and explain that the app may not be working.

   관리팀

   management team

   직접

   directly

   연락해서

   contacting and then

   앱

   app

   작동하지 않을 수도

   may not work

   설명해

   explain

   More detail

   관리팀 means “management team.” 관리 relates to management or maintenance, and 팀 means “team.” Together, this can name the team responsible for managing or maintaining a place or service. Here it is the team to be contacted. 직접 means “directly,” emphasizing that the contact is made without an intermediary. Example: 직접 물어봐요. — “Ask directly.” 연락해서 comes from 연락하다, “to contact.” The connective ending -해서 links this action to the following action, giving “contact and then…” in this sentence. Example: 친구에게 연락해서 물어봤어요. — “I contacted my friend and asked.” The particle -에 in 관리팀에 marks the recipient or target of the contact; it is not an object marker. The imperative subject is understood as the person being addressed. 앱 means “app,” a noun commonly used for an application on a device. It is marked with 이, which identifies it as the subject of the following description. 작동하지 않을 수도 expresses the possibility that something may not work. 작동하다 means “to operate” or “to work”; 작동하지 않다 negates it, and -(으)ㄹ 수도 있다 expresses one possible situation. In this sentence, the form continues into 있다고: 작동하지 않을 수도 있다고 means “that it may not be working.” Example: 컴퓨터가 작동하지 않을 수도 있어요. — “The computer may not work.” 설명해 comes from 설명하다, “to explain.” In this plain-style imperative, -해 tells the addressee to explain. The following -다고 marks the content being explained: the app’s possible failure to operate. Together, 관리팀에 직접 연락해서 means “contact the management team directly and then,” and 앱이 작동하지 않을 수도 있다고 설명해 means “explain that the app may not be working.” The full utterance is: “Contact them directly and explain that the app may not be working.”

9. 무슨 일이 있었는지 알 때까지 화면을 계속 열어 둘 수 있어.

   I can keep the screen open until I know what happened.

   무슨 일이 있었는지

   what happened

   알 때까지

   until knowing

   화면

   screen

   계속

   continuously

   열어 둘

   keep open

   수 있어

   can

   More detail

   무슨 일이 있었는지 means “what happened.” 무슨 일 is a reusable way to ask about an unspecified matter or event, while 있었는지 uses the past form of 있다 in the embedded-question ending -는지. This turns the question into something that can be referred to inside a larger sentence. Example: 무슨 일이 있었는지 말해 주세요. — “Please tell me what happened.” 알 때까지 means “until knowing.” 알 is the form of 알다 used before 때 (“time”), and 까지 marks the endpoint “until.” The subject is omitted in Korean; in this sentence, the fixed translation identifies it as “I.” Example: 이유를 알 때까지 기다려요. — “I wait until I know the reason.” 화면 means “screen.” Here 화면을 uses the object marker -을, showing that the screen is the object of the following action. Example: 화면을 확인해 주세요. — “Please check the screen.” 계속 is an adverb meaning “continuously” or “continually,” describing an action that continues over time. Example: 계속 기다리고 있어요. — “I am still waiting.” 열어 둘 expresses “keep open.” 열다 means “to open,” and -어 두다 adds the idea of leaving something in an achieved state so that it remains that way. In -어 둘 수 있어, 두다 appears as 둘 before the ability construction. Example: 문을 열어 둘게요. — “I’ll leave the door open.” 수 있어 is the informal sentence-ending form of the ability construction 동사-(으)ㄹ 수 있다, meaning “can” or “be able to.” Here it applies to 열어 둘, so the possible action is keeping the screen open. This form expresses possibility or ability; it does not by itself say that the action is already happening. Together, 무슨 일이 있었는지 알 때까지 sets the endpoint: until the speaker knows what happened. 화면을 계속 열어 둘 수 있어 says that the speaker can keep the screen open until then. The complete meaning is “I can keep the screen open until I know what happened.”

10. 그러면 관리팀에서 화면 캡처를 보고 무엇이 잘못됐는지 알 수 있어.

    Then maintenance can use the screenshot to understand what went wrong.

    그러면

    then; in that case

    관리팀

    maintenance team

    화면 캡처

    screen capture; screenshot

    보고

    looking at; seeing

    무엇이

    what (as the subject)

    잘못됐는지

    what went wrong

    알 수 있어

    can know; can find out

    More detail

    그러면 sets up a consequence from the preceding situation: “then” or “in that case.” It connects a condition or newly established fact to what follows. 관리팀 means “the maintenance team” here. 팀 means “team,” while 관리 specifies the team’s area of responsibility. In the full sentence, 관리팀에서 uses 에서 to mark the organization carrying out the action: “the maintenance team can …” 화면 캡처 is a compound noun meaning “screen capture” or “screenshot.” 화면 means “screen,” and 캡처 is a commonly used loanword for a captured image. Together, they name the image being examined. 보고 comes from 보다, “to see” or “to look at.” The ending -고 connects this action with the following action; here, looking at the screenshot is the means or basis for finding out what went wrong. Example: 사진을 보고 알았어요 means “I found out by looking at the photo.” 무엇이 consists of 무엇 (“what”) plus the subject marker 이. It marks “what” as the thing that has the relevant state in the embedded question. The marker is used because 무엇 is the subject of the following expression. 잘못됐는지 comes from 잘못되다, “to go wrong” or “to be incorrect.” It contains the contracted past form 됐 from 되었 and the embedded-question ending -는지; 잘못됐는지 therefore means “whether it went wrong” or, with 무엇이, “what went wrong.” Example: 무엇이 잘못됐는지 확인하세요 means “Check what went wrong.” 알 수 있어 uses 알다, “to know,” with -(으)ㄹ 수 있다, a construction expressing possibility or ability. It means “can know” or “can find out.” Here 있어 is the plain, non-honorific form of 있다, so the ending is informal rather than polite. This construction says that the information can be determined; it does not say that it is already known. Together, 화면 캡처를 보고 means “by looking at the screenshot,” and 무엇이 잘못됐는지 알 수 있어 means “can find out what went wrong.” With 그러면 and 관리팀에서, the complete meaning is: “Then the maintenance team can use the screenshot to understand what went wrong.”