GraphQL API returns clear errors for trigger tags and chart updates

Creating a trigger with a tag that has no value now returns a validation error. Chart mutations return validation errors instead of server errors for unsupported input. If you manage triggers and dashboards from scripts or AI agents, you now get an error you can act on.

Trigger tags need a value

Until now, AppSignal saved a trigger with a tag that had a key but no value. That one trigger could stop AppSignal from syncing all of the app's settings, including its other triggers.

Now AppSignal rejects the trigger straight away with the error Tags must each have a key and a text value. This also applies to triggers created or updated with AppSignal MCP.

Chart updates say what to fix

• Updating a chart with the wrong mutation for its type now returns an error that says the chart is a number or timeseries chart, so you know which mutation to use. Until now, it returned a server error that didn't say why.
• Tags on a timeseries chart go on each metric. The API no longer accepts tags on the chart itself, and sending them returns an error.

Read the GraphQL mutations docs for which mutation to use for each chart type.