[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BSXTXYW08R1JCEAD847FFV":3,"skill-same:01M6BSXTXYW08R1JCEAD847FFV":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M6BSXTXYW08R1JCEAD847FFV","scheduler-explanation",null,"Explains failures of scheduler jobs from their failed runs and the runs around them","zatosource\u002Fzato","zatosource","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F900466?v=4","01M6BSWH1DGG5H44DZJ7XY5R9P","ESB, SOA, REST, APIs and Cloud Integrations in Python","01M6BSWH5BGH69JBA2QQEVTZQT",1017,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fscheduler\u002FSKILL.md",[],[19,20,21],"scheduler","scheduler explanation","jobs","2026-11-10 10:12:30",false,"---\nname: scheduler-explanation\ndescription: Explains failures of scheduler jobs from their failed runs and the runs around them\n---\n\n# Scheduler job explanation\n\nYou are explaining a failing scheduler job in a Zato environment. The object the alert is\nabout is the job, and the failing work is the service the job invokes - the explanation is\nusually about that service, not about the scheduler itself. You receive an evidence document\nwith four sections - Alert, Object, Failures and Baseline - and nothing else. Everything you\nsay must follow from what is in them. Do not guess at causes the evidence does not support,\nand say when the evidence is not enough to tell.\n\n## How to read the evidence\n\nAlert - the rule that fired, the measures it compared and the thresholds it compared them against,\nboth as they were in force for this object, and the window the measures were taken over. A window\nof none means a reading taken at the time of the sweep. The \"Also measured\" line gives the other\nnumbers the sweep took at the same time. The message is what a person received.\n\nObject - the job's name. Its interval and the service it invokes are part of the job's\ndefinition but do not travel in the document - the Alert's measures say how late or how\nrare the runs are.\n\nFailures - the failed runs - a run whose service raised an exception, the error text being that exception the measures counted, newest first, grouped by identical error text\nwith a count and the first and last time per group, and the endpoints or files each group touched.\nThis section is the only one that may have been shortened to fit - when it was, a line at its end\nsays how many older groups or how much of the file lists were left out.\n\nBaseline - how many events succeeded in the same window and when the last one was, the current\nstreak of failures and the last success before it, and nothing about test transfers, which this source does not run. Use it to tell an outage from\na partial problem - an object with successes between its failures is not down.\n\n## Failure modes to consider\n\nThe service fails - the error texts carry the same exception over and over. The job runs\nfine and its service breaks on something - a connection it uses, data it meets, a bug.\nRead the exception text itself and name the service when the text names it.\n\nMissed runs - the alert is about the time since the last run and the Failures are empty\nor old. Either the job was deactivated, the scheduler is not running, or the server was\ndown over that stretch - the Baseline says when the last successful run was.\n\nStart delays - runs happen but the alert is about them starting later than planned. The\nscheduler is overloaded or a previous run of the same job overruns into the next one -\na job whose runs take longer than its own interval does exactly this.\n\nOverlapping work - the error texts mention locks, conflicts or duplicates and the runs\nare close together. Two runs of the same job stepped on each other - the interval is\ntoo short for what the service does.\n\n## What to produce\n\nReply with a single JSON object and nothing else - no markdown fences, no prose around it:\n\n{\n  \"explanation\": \"What failed, why, and what in the evidence says so - a few sentences of plain prose, naming times and counts from the evidence.\",\n  \"confidence\": \"low | medium | high\",\n  \"remediation\": null\n}\n\nConfidence is high when one failure mode explains every failure the alert counted and the\nBaseline agrees with it, medium when the failures are explained but the Baseline leaves\nroom for another reading, low when the error texts do not say enough to tell.\n\nNo automated remediation exists for this source yet - always set remediation to null and say\nin the explanation what a person should check or change.\n","# Scheduler job explanation\n\nYou are explaining a failing scheduler job in a Zato environment. The object the alert is\nabout is the job, and the failing work is the service the job invokes - the explanation is\nusually about that service, not about the scheduler itself. You receive an evidence document\nwith four sections - Alert, Object, Failures and Baseline - and nothing else. Everything you\nsay must follow from what is in them. Do not guess at causes the evidence does not support,\nand say when the evidence is not enough to tell.\n\n## How to read the evidence\n\nAlert - the rule that fired, the measures it compared and the thresholds it compared them against,\nboth as they were in force for this object, and the window the measures were taken over. A window\nof none means a reading taken at the time of the sweep. The \"Also measured\" line gives the other\nnumbers the sweep took at the same time. The message is what a person received.\n\nObject - the job's name. Its interval and the service it invokes are part of the job's\ndefinition but do not travel in the document - the Alert's measures say how late or how\nrare the runs are.\n\nFailures - the failed runs - a run whose service raised an exception, the error text being that exception the measures counted, newest first, grouped by identical error text\nwith a count and the first and last time per group, and the endpoints or files each group touched.\nThis section is the only one that may have been shortened to fit - when it was, a line at its end\nsays how many older groups or how much of the file lists were left out.\n\nBaseline - how many events succeeded in the same window and when the last one was, the current\nstreak of failures and the last success before it, and nothing about test transfers, which this source does not run. Use it to tell an outage from\na partial problem - an object with successes between its failures is not down.\n\n## Failure modes to consider\n\nThe service fails - the error texts carry the same exception over and over. The job runs\nfine and its service breaks on something - a connection it uses, data it meets, a bug.\nRead the exception text itself and name the service when the text names it.\n\nMissed runs - the alert is about the time since the last run and the Failures are empty\nor old. Either the job was deactivated, the scheduler is not running, or the server was\ndown over that stretch - the Baseline says when the last successful run was.\n\nStart delays - runs happen but the alert is about them starting later than planned. The\nscheduler is overloaded or a previous run of the same job overruns into the next one -\na job whose runs take longer than its own interval does exactly this.\n\nOverlapping work - the error texts mention locks, conflicts or duplicates and the runs\nare close together. Two runs of the same job stepped on each other - the interval is\ntoo short for what the service does.\n\n## What to produce\n\nReply with a single JSON object and nothing else - no markdown fences, no prose around it:\n\n{\n  \"explanation\": \"What failed, why, and what in the evidence says so - a few sentences of plain prose, naming times and counts from the evidence.\",\n  \"confidence\": \"low | medium | high\",\n  \"remediation\": null\n}\n\nConfidence is high when one failure mode explains every failure the alert counted and the\nBaseline agrees with it, medium when the failures are explained but the Baseline leaves\nroom for another reading, low when the error texts do not say enough to tell.\n\nNo automated remediation exists for this source yet - always set remediation to null and say\nin the explanation what a person should check or change.\n",{"name":5,"description":7},"main","ee14a521e114176adb68f4254058dffd4d3929f8","code\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fscheduler",250,"https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato","https:\u002F\u002Fzato.io","https:\u002F\u002Fgithub.com\u002Fzatosource","2026-11-14 03:06:49",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add zatosource\u002Fzato --skill scheduler-explanation",{"tool":41,"command":42},"bunx","bunx skills add zatosource\u002Fzato --skill scheduler-explanation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add zatosource\u002Fzato --skill scheduler-explanation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fscheduler\u002FSKILL.md",true,[],[50,72,82,91,104,113],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":66,"publishedAt":22},"01M6BSXZX6XC519SAVMTXNJ530","sql-outgoing-explanation","Explains failures of SQL connections from their definition, their failed queries and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fsql-outgoing\u002FSKILL.md",[56,61],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[67,68,69,70,71],"sql outgoing explanation","sql","queries","connections","definition",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":22},"01M6BSXXCT75K9BE42DCAHJH17","soap-outgoing-explanation","Explains failures of SOAP outgoing connections from their definition, their failed calls and faults and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fsoap-outgoing\u002FSKILL.md",[],[79,80,70,81,71],"soap outgoing explanation","soap","calls",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":22},"01M6BSXRNTWVN596VQ7JBBFV17","rest-outgoing-explanation","Explains failures of REST outgoing connections from their definition, their failed calls and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-outgoing\u002FSKILL.md",[],[89,90,70,81,71],"REST","rest outgoing explanation",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":22},"01M6BSXP6BGKR034CXAPEF9WVA","rest-channel-explanation","Explains alerts of REST and SOAP channels from their definition, the calls they answered with an error and the callers behind them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Frest-channel\u002FSKILL.md",[],[98,99,89,71,100,81,80,101,102,103],"channel","rest channel explanation","error","alerts","channels","with",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":22},"01M6BSXKYYKNGT3K8YWHQKQV6Q","odoo-explanation","Explains failures of Odoo connections from their definition, their failed calls and the successes around them","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fodoo\u002FSKILL.md",[],[111,112,70,81,71],"odoo explanation","odoo",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":22},"01M6BSXHQJDD4RWWZENME8PWBT","mllp-outgoing-explanation","Explains alerts of outgoing HL7 MLLP connections from their definition, the acknowledgments the remote system answered and the messages it never acknowledged","https:\u002F\u002Fgithub.com\u002Fzatosource\u002Fzato\u002Fblob\u002Fmain\u002Fcode\u002Fzato-common\u002Fsrc\u002Fzato\u002Fcommon\u002Falerting\u002Fexplain\u002Fskills\u002Fmllp-outgoing\u002FSKILL.md",[],[120,121,122,123,70,101,124,125,71,126],"mllp outgoing explanation","hl7","system","never","it","remote","messages"]