Skip to content
1stLine Docs 1stLine Docs

Alerts&Schemas Troubleshooting

Use this page when Alert Schema creation, extraction, forwarding, or testing does not behave as expected.

You cannot create or edit Alert Schemas

The UI can show You do not have permission to create or edit alert schemas.

Ask an organization admin to update your Role or have someone with configuration access create the schema.

See Access Control for more information.

No Library Schema matches your producer

The Library Schema screen can show No schemas match your search or No library schemas available.

Create a custom schema from a real alert payload instead. See Create Custom Schema.

Schema creation token expired

The create flow can show Token expired. Please create a new token.

Start the custom schema flow again. Schema Creation Tokens are short-lived setup tokens.

Schema creation was aborted

The create flow can show Schema creation aborted.

Open Create Alert Schema and start again when you are ready to send a new example payload.

Pattern test says Invalid JSON payload

The Test Pattern Extraction view expects valid JSON in Alert Payload.

Fix the JSON and click Test Patterns again.

Pattern extraction returns no fields

Check:

  • the sample payload matches the real Alert Producer payload
  • sourceField points to the field that contains the data
  • the Source Pattern type matches the data shape
  • fallback patterns are configured when the payload can vary
  • Fields match the names produced by Patterns

Use Extraction Steps to see where extraction stopped.

Alert Instance is created but not routed

If an Alert Instance appears as Orphan, create or update a Routing Rule for the Alert Schema.

For a first test, use a catch-all Routing Condition. Tighten the Conditions after you confirm the flow works.

Alert does not reach the Alert Receiver

Check:

  • Alert Producer Destination was copied from the correct schema
  • the forwardTo placeholder was replaced with the real Alert Receiver destination
  • Default Forward To is set if the producer request does not include forwardTo
  • the schema is enabled
  • the Alert Producer sends JSON that 1stLine can process

For normal Alert Producer traffic, 1stLine needs either forwardTo or Default Forward To to forward the alert.

Transformation result is wrong

Check Patterns first. Transformation Templates use the extracted context.

Then check:

  • Transformation Template JSON is a JSON object at the root
  • placeholders use ${field} or ${field:-}
  • nested paths and array indexes match the extracted field names
  • action-link fields point to paths that exist in the outbound payload

Use Test transformation and review Transformation Result.

Remember that Transformation Template only supports ${field} and ${field:-}.

If you want fallback text such as ${field:-fallback text}, use mapping overrides instead of the Transformation Template.

Recurrences increase but the receiver does not get another message

Check Schema Config and review Proxy recurrent alerts.

  • If it is off, repeated firing alerts still update the same Alert Instance and increase Recurrences, but 1stLine suppresses forwarding of those repeated firing messages.
  • If you want every repeated firing occurrence to reach the receiver, turn Proxy recurrent alerts on.

Incident lifecycle updates do not forward

Check:

  • Incident Lifecycle Mapping has a trigger configured for the Incident event
  • Send Alert is enabled if you expect an update notification
  • Register Alert is enabled if you expect a new Alert Instance
  • the original Alert Instance has forwardTo, or the schema has Default Forward To

Lifecycle messages follow the same forwarding rule as firing alerts: original forwardTo first, then Default Forward To.